Fedora Final Release
Set the variable to True in ansible repository.
Set the bodhi release to
$ bodhi releases edit --name F40 --state current
Set the bodhi stable tag to point to updates instead of base repo
$ bodhi releases edit --name F40 --stable-tag f40-updates
Set EOL of oldest release to corret date
$ bodhi releases edit --name F38 --eol YYYY-MM-DD
$ bodhi releases edit --name F38C --eol YYYY-MM-DD
$ bodhi releases edit --name F38F --eol YYYY-MM-DD
$ bodhi releases edit --name F38M --eol YYYY-MM-DD
Now that we have a final GOLD compose, we dont need nightly branched composes anymore. This is disabled in releng role in infra ansible repo and then running the playbook.
$ sudo rbac-playbook groups/releng-compose.yml
Lift the RelEng Freeze so that the updates will be pushed to stable. This is done by editing RelEngFrozen variable in infra ansible repo and then run the bodhi playbook.
$ sudo rbac-playbook groups/bodhi-backend.yml
In pungi.rpm.conf.j2 we need to check that the release.version_int should be now pointing to 41 for all the artifacts that compose location is going to be under /compose/branched/. For the reference pungi.rpm.conf.j2 check.
For the references, checkout this PR.
To prepare for running the staging script, make sure you have the following information:
Release Version: This is the numerical version number of the release, for example, 40.
ComposeID: The ID associated with the Compose, such as "Fedora-40-20160614.0".
Label: The label used for the location in stage, for example, "Compsoe label for the location in stage 39_RC-1.2."
Key: The name of the release key, which can be "fedora-40" or "fedora-40-secondary," as examples.
Prerelease: Set this to 0 or 1 to determine if the release should be placed in a testing environment or not.
Arch (Optional): For secondary architectures, this parameter can be used to make changes to some internal locations.
$ scripts/stage-release.sh 40 Fedora-40-20160614.0 40_RC-1.2 fedora-40 0
Sync the release to the Red Hat internal archive following internally documented
Make sure to grab the directory size usage numbers which is used to send an email to email@example.com list.
check PDC for active releases and respective EOL date
if needed run the adjust-eol-all.py script from releng repository to correct any mistakes
Sometimes builds are not properly tagged during the freeze process. Make sure all builds are properly tagged, for more info about the [issue](https://pagure.io/releng/issue/11775)
Verification is somewhat difficult as one cannot look at the content via the web server due to permissions. Typically we ask somebody from the Infrastructure team to give the tree a second set of eyes.
Want to help? Learn how to contribute to Fedora Docs ›