From 47b3c6b3081591689d19c5936c1ccbc1a1b429cd Mon Sep 17 00:00:00 2001 From: Tomas Hrcka Date: May 15 2023 11:29:16 +0000 Subject: [releng] Fix EOL sop Signed-off-by: Tomas Hrcka --- diff --git a/modules/release_guide/pages/release_eol.adoc b/modules/release_guide/pages/release_eol.adoc index 44dccb6..f05caf8 100644 --- a/modules/release_guide/pages/release_eol.adoc +++ b/modules/release_guide/pages/release_eol.adoc @@ -8,7 +8,8 @@ Each release of Fedora is maintained as laid out in the https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#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. +necessary to move a release to that status. To get the correct EOL date visit +https://fedorapeople.org/groups/schedule/f-{branched}/f-{branched}-key-tasks.html[release schedule] for the last release. === Actions @@ -47,16 +48,18 @@ and the script on compose-branched01.iad2.fedoraproject.org * Set PDC *active* value for the release to *False* +[source,subs="attributes+"] .... -curl -u: -H 'Authorization: Token ' -H 'Accept: application/json' -H 'Content-Type:application/json' -X PATCH -d '{"active":"false"}' https://pdc.fedoraproject.org/rest_api/v1/releases/fedora-31/ +curl -u: -H 'Authorization: Token ' -H 'Accept: application/json' -H 'Content-Type:application/json' -X PATCH -d '{"active":"false"}' https://pdc.fedoraproject.org/rest_api/v1/releases/fedora-{old_release}/ .... * Set the EOL dates in PDC for all the components to the release EOL date if they are not already set. Run the following script from https://pagure.io/releng[releng] repo +[source,subs="attributes+"] .... -python scripts/pdc/adjust-eol-all.py f31 2020-11-24 +python scripts/pdc/adjust-eol-all.py f{old_release} 2020-11-24 .... ==== Bodhi tasks