Infrastructure/infra-docs-fpo
1
0
Fork 0
Code Issues 100 Pull requests 6 Projects Releases Packages Wiki Activity Actions

[releng] Fix EOL sop

Browse source 
Signed-off-by: Tomas Hrcka <thrcka@redhat.com>
This commit is contained in:
Tomáš Hrčka 2023-05-15 13:20:56 +02:00
parent f03fde0f5a
commit 47b3c6b308
1 changed files with 6 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

9
modules/release_guide/pages/release_eol.adoc
View file

@ -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 <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 <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 <token> f31 2020-11-24
python scripts/pdc/adjust-eol-all.py <token> f{old_release} 2020-11-24
....
==== Bodhi tasks