From 070b9a24fc3f8c32a76a00d16117043ccd3f2be1 Mon Sep 17 00:00:00 2001 From: Adam Williamson Date: Tue, 26 Nov 2024 09:23:33 -0800 Subject: [PATCH] EOL SOP: various updates * Link to docs.fp.o not the wiki * Send announcements to test@ as well as test-announce@ * Only update fedora-appstream-metadata package if necessary * Don't use bullets in sections with only one instruction * Drop the FNNM release from Bodhi commands (no longer exists) * Clean up the flow of ansible section a bit * Correct syntax for the rbac-playbook command Signed-off-by: Adam Williamson --- modules/release_guide/pages/release_eol.adoc | 35 ++++++++++---------- 1 file changed, 18 insertions(+), 17 deletions(-) diff --git a/modules/release_guide/pages/release_eol.adoc b/modules/release_guide/pages/release_eol.adoc index 051b0d5..455f41a 100644 --- a/modules/release_guide/pages/release_eol.adoc +++ b/modules/release_guide/pages/release_eol.adoc @@ -5,7 +5,7 @@ include::_partials/attributes.adoc[] == Description Each release of Fedora is maintained as laid out in the -https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule[maintenance +https://docs.fedoraproject.org/en-US/releases/lifecycle/#_maintenance_schedule[maintenance schedule]. At the conclusion of the maintenance period, a Fedora release enters `end of life` status. This procedure describes the tasks necessary to move a release to that status. To get the correct EOL date visit @@ -15,8 +15,8 @@ https://fedorapeople.org/groups/schedule/f-{branched}/f-{branched}-key-tasks.htm === Reminder announcement -Send an email to `devel@`, `devel-announce@`, `test-announce@`, `announce@` lists as remainder about the release EOL. -Use https://pagure.io/releng/blob/main/f/mail-templates/08-end-of-life.txt[template] from release engineering repo +Around a week before the EOL date, end an email to `devel@`, `devel-announce@`, `test@`, `test-announce@`, `announce@` lists as remainder about the release EOL. +Use the https://pagure.io/releng/blob/main/f/mail-templates/08-end-of-life.txt[template] from release engineering repo. [NOTE] ==== @@ -25,13 +25,15 @@ Please ensure that the reminder email is scheduled to be sent one week before th === `fedora-appstream-metadata` package update -Update the +If necessary, update the https://src.fedoraproject.org/rpms/fedora-appstream-metadata[`fedora-appstream-metadata`] package with the new EOL date. Follow the instructions from the repo README. Build the package, create an update and make sure it lands in the stable repo before proceeding. +This is not necessary if the package already has the correct EOL date. + === Koji tasks * Disable builds by removing targets @@ -79,32 +81,32 @@ xref:releng_misc_guide:sop_pushing_updates.adoc[Pushing Updates SOP]. === Bodhi tasks -* Run the following bodhi commands to set the releases state to +Run the following bodhi commands to set the releases state to *archived* [source,subs="attributes+"] .... $ bodhi releases edit --name "F{old_release}" --state archived -$ bodhi releases edit --name "F{old_release}M" --state archived $ bodhi releases edit --name "F{old_release}C" --state archived $ bodhi releases edit --name "F{old_release}F" --state archived .... === Fedora Infra Ansible Changes -* We need to make changes to bodhi, koji, mbs, releng, autosign roles in -ansible repo. +We need to make some changes and then run several roles in the ansible repo. ==== Update FedoraPreviousPrevious.yaml in ansible repository -* Set the variable to False +Edit /vars/all/FedoraPreviousPrevious.yaml and set the value to `False`. ==== Adjust the EOL for gnome-software -* Edit /roles/pkgdb-proxy/files/pkgdb-gnome-software-collections.json in ansible -and set the release to status "EOL" +Edit /roles/pkgdb-proxy/files/pkgdb-gnome-software-collections.json in ansible +and set the release to status "EOL". -* Run the associated playbooks on _batcave_ +==== Run the playbooks + +First, push the above edits. Then run the associated playbooks on _batcave01_: .... $ sudo ansible-playbook /srv/web/infra/ansible/playbooks/groups/bodhi-backend.yml @@ -117,15 +119,14 @@ $ sudo ansible-playbook /srv/web/infra/ansible/playbooks/openshift-apps/bodhi.ym [NOTE] ==== -Another way to run the playbook is using rbac-playbook, in case one don't have sysadmin-main rights or can't become root. -Syntax: sudo rbac-playbook mbs.yml +Another way to run the playbook is using rbac-playbook, in case you don't have sysadmin-main rights or can't become root. +Syntax: sudo rbac-playbook groups/bodhi-backend.yml ==== === Final announcement -* Send the final announcement to `devel@`, `devel-announce@`, `test-announce@`, `announce@` lists. - -Use https://pagure.io/releng/blob/main/f/mail-templates/07-end-of-life.txt[template] from release engineering repo +Send the final announcement to `devel@`, `devel-announce@`, `test@`, `test-announce@`, `announce@` lists. +Use the https://pagure.io/releng/blob/main/f/mail-templates/08-end-of-life.txt[template] from release engineering repo. ==== stage the EOL release to archive