Fedora Final Release

Update FedoraPreviousPrevious.yaml in ansible repository

Set the variable to True in ansible repository.

Koji changes

$ koji edit-tag --lock f39
$ koji edit-tag --lock f39-modular

Bodhi Changes

Set the bodhi release to current

$ bodhi releases edit --name F39 --state current

Set the bodhi stable tag to point to updates instead of base repo

$ bodhi releases edit --name F39 --stable-tag f39-updates

Set EOL of oldest release to corret date

$ bodhi releases edit --name F37 --eol YYYY-MM-DD
$ bodhi releases edit --name F37C --eol YYYY-MM-DD
$ bodhi releases edit --name F37F --eol YYYY-MM-DD
$ bodhi releases edit --name F37M --eol YYYY-MM-DD

Disable Branched Compose

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 RelEng freeze

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

Stage Final Release for Mirrors

  1. Gather the needed info for running the staging script: Release Version: the numerical version number of the release 39 ComposeID: The ID of the Compose Label: Compsoe label for the location in stage 39_RC-1.2 for example Key: the name of teh release key fedora-39 or fedora-39-secondary as examples Prerelease: 0 or 1 sets if the release goes in test/ or not Arch: <optional> For secondary arches, changes some internal locations

    $ scripts/stage-release.sh 39 Fedora-39-20160614.0 39_RC-1.2 fedora-39 0
  2. Sync the release to the Red Hat internal archive following internally documented

Check and set EOL on previous releases to reflect reality

  1. check PDC for active releases and respective EOL date

  2. if needed run the adjust-eol-all.py script from releng repository to correct any mistakes


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.