From 26f894b4173d3f5a84716679b51c4cfc541cbbef Mon Sep 17 00:00:00 2001 From: Louis Abel Date: Tue, 19 Jul 2022 00:09:36 -0700 Subject: [PATCH] start a release wiki page --- docs/.pages | 1 + docs/sop/.pages | 4 +++ docs/sop/index.md | 8 +++++ docs/sop/sop_release.md | 75 +++++++++++++++++++++++++++++++++++++++++ 4 files changed, 88 insertions(+) create mode 100644 docs/sop/.pages create mode 100644 docs/sop/index.md create mode 100644 docs/sop/sop_release.md diff --git a/docs/.pages b/docs/.pages index 8fa8a40..26a1d07 100644 --- a/docs/.pages +++ b/docs/.pages @@ -3,4 +3,5 @@ nav: - ... | index.md - ... | about.md - Documentation | documentation + - SOP | sop ... diff --git a/docs/sop/.pages b/docs/sop/.pages new file mode 100644 index 0000000..fa02d00 --- /dev/null +++ b/docs/sop/.pages @@ -0,0 +1,4 @@ +--- nav: + - ... | index.md + - Release Procedures | sop_release.md +... diff --git a/docs/sop/index.md b/docs/sop/index.md new file mode 100644 index 0000000..6cf7a01 --- /dev/null +++ b/docs/sop/index.md @@ -0,0 +1,8 @@ +--- +title: SOP (Standard Operationg Procedures) +--- + +This section goes over the various SOP's for SIG/Core. Please use the menu items +to find the various pages of interest. + +{% include "resources_bottom.md" %} diff --git a/docs/sop/sop_release.md b/docs/sop/sop_release.md new file mode 100644 index 0000000..e311845 --- /dev/null +++ b/docs/sop/sop_release.md @@ -0,0 +1,75 @@ +--- +title: Rocky Release Procedures for SIG/Core (RelEng/Infrastructure) +--- + +This SOP contains all the steps required by SIG/Core (a mix of Release +Engineering and Infrastructure) to perform releases of all Rocky Linux +versions. Work is in all collaboration within the entire group of +engineerings. + +## Contact Information + +| | | +| - | - | +| **Owner** | SIG/Core (Release Engineering & Infrastructure) | +| **Email Contact** | infrastructure@rockylinux.org | +| **Email Contact** | releng@rockylinux.org | +| **Mattermost Contacts** | `@label` `@neil` `@tgo` `@skip77` `@mustafa` `@sherif` `@pgreco` | +| **Mattermost Channels** | `~Infrastructure` | + +## Preparation + +## Notes about Release Day + +Within a minimum of two (2) days, the following should be true: + +1. Torrents should be setup. All files can be synced with the seed box(es) but +not yet published. The data should be verified using sha256sum and compared to +the CHECKSUM files provided with the files. + +2. Website should be ready (typically with an open PR in github). The content +should be verified that the design and content are correct and finalized. + +3. Enough mirrors should be setup. This essentially means that all content for +a release should be synced to our primary mirror with the executable bit turned +off, and the content should also be hard linked. In theory, mirror manager can +be queried to verify if mirrors are or appear to be in sync. + +## Notes about Patch Days + +## Prior to Release Day notes + +## Release Day + +## Priorities + +During release day, these should be verified/completed in order: + +1. Website - The primary website and user landing at rockylinux.org should allow +the user to efficiently click through to a download link of an ISO, image, or +torrent. It must be kept up. + +2. Torrent - The seed box(es) should be primed and ready to go for users +downloading via torrent. + +3. Release Notes & Documentation - The release notes are often on the same +website as the documentation. The main website and where applicable in the docs +should refer to the Release Notes of Rocky Linux. + +4. Wiki - If applicable, the necessary changes and resources should be available +for a release. In particular, if a major release has new repos, changed repo names, +this should be documented. + +5. Everything else! + +## Resources + +## SIG/Core Checklist + +### Beta + +### Release Candidate + +### Final + +{% include "resources_bottom.md" %}