Update final_release sop with more stuffs and concise manner

Signed-off-by: Samyak Jain <samyak.jn11@gmail.com>
This commit is contained in:
Samyak Jain 2023-11-03 14:48:44 +05:30 committed by humaton
parent ce501524ec
commit 60e69681c0

View file

@ -37,7 +37,9 @@ $ bodhi releases edit --name F{old_release}F --eol YYYY-MM-DD
$ bodhi releases edit --name F{old_release}M --eol YYYY-MM-DD $ bodhi releases edit --name F{old_release}M --eol YYYY-MM-DD
.... ....
== Disable Branched Compose == Ansible Changes
=== Disable Branched Compose
Now that we have a final GOLD compose, we dont need nightly branched Now that we have a final GOLD compose, we dont need nightly branched
composes anymore. This is disabled in composes anymore. This is disabled in
@ -48,7 +50,7 @@ role] in infra ansible repo and then running the playbook.
$ sudo rbac-playbook groups/releng-compose.yml $ sudo rbac-playbook groups/releng-compose.yml
.... ....
== Lift RelEng freeze === Lift RelEng freeze
Lift the RelEng Freeze so that the updates will be pushed to stable. Lift the RelEng Freeze so that the updates will be pushed to stable.
This is done by editing This is done by editing
@ -59,15 +61,35 @@ variable] in infra ansible repo and then run the bodhi playbook.
$ sudo rbac-playbook groups/bodhi-backend.yml $ sudo rbac-playbook groups/bodhi-backend.yml
.... ....
=== Update Release Versions
In pungi.rpm.conf.j2 we need to check that the release.version_int should be now pointing to {rawhide} for all the artifacts that compose location is going to be under /compose/branched/. For the reference https://pagure.io/fork/jnsamyak/fedora-infra/ansible/c/cf05a84bfd652b264dc74eef29a453a55be565c1[pungi.rpm.conf.j2] check.
=== Update releng roles updates
. https://pagure.io/fedora-infra/ansible/blob/main/f/roles/releng/files/cloud-updates[cloud-updates]: Remove the commented version and append a new entry for {branched}.
. https://pagure.io/fedora-infra/ansible/blob/main/f/roles/releng/files/container-updates[container-updates]: Remove the commented version and append a new entry for {branched}.
. Update https://pagure.io/fedora-infra/ansible/blob/main/f/vars/all/00-FedoraCycleNumber.yaml[FedoraCycleNumber] to {branched}.
. Update https://pagure.io/fedora-infra/ansible/blob/main/f/vars/all/FedoraBranchedBodhi.yaml[FedoraBranchedBodhi] to current.
. Set https://pagure.io/fedora-infra/ansible/blob/main/f/vars/all/FedoraPreviousPrevious.yaml[FedoraPreviousPrevious] to True.
For the references, checkout this https://pagure.io/fork/jnsamyak/fedora-infra/ansible/c/6d1267970e09f412f1f51a2c203ae64e29e2c4c3[PR].
== Stage Final Release for Mirrors == Stage Final Release for Mirrors
. Gather the needed info for running the staging script: Release To prepare for running the staging script, make sure you have the following information:
Version: the numerical version number of the release `{branched}` ComposeID: The
ID of the Compose Label: Compsoe label for the location in stage . Release Version: This is the numerical version number of the release, for example, {branched}.
`{branched}_RC-1.2` for example Key: the name of teh release key `fedora-{branched}` or . ComposeID: The ID associated with the Compose, such as "Fedora-{branched}-20160614.0".
`fedora-{branched}-secondary` as examples Prerelease: 0 or 1 sets if the release . Label: The label used for the location in stage, for example, "Compsoe label for the location in stage 39_RC-1.2."
goes in test/ or not Arch: <optional> For secondary arches, changes some . Key: The name of the release key, which can be "fedora-{branched}" or "fedora-{branched}-secondary," as examples.
internal locations . 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.
+ +
[source,subs="attributes+"] [source,subs="attributes+"]
.... ....