Fedora Final Freeze
Before freezing everything we need to do the last stable push in bodhi.
Ansible changes
Freeze is enabled by editing RelEngFrozen variable in infra ansible repo and then run the bodhi playbook. This playbook should be executed on the 'batcave01' machine. Please note that the 'rbac-playbook' command utilizes role-based access control (RBAC) and verifies that you are in the correct group with the necessary privileges. If you meet these requirements, you can run the playbook without needing root access.
$ ssh batcave01.iad2.fedoraproject.org
$ sudo rbac-playbook groups/bodhi-backend.ymlUpdate bodhi release
$ bodhi releases edit --name F41 --state frozenReminder announcement
Send an email as mentioned below to devel@, devel-announce@, test-announce@, announce@ lists as information that the final freeze is now active.
For the reference, you can refer generic template for final freeze from release engineering repo.
Hi all,
Today, YYYY-MM-DD, is an important day on the Fedora Linux 41 schedule
[1], with significant cut-offs.
Today we have the Final Freeze [2] which starts at 14:00 UTC. This means
that only packages which fix accepted blocker or freeze exception bugs
[3][4][5] will be marked as 'stable' and included in the Final composes.
Other builds will remain in updates-testing until the Final release is
approved, at which point the Final freeze is lifted and packages can
move to the 'updates' repository. Pending updates will be pushed before
final release as zero day updates.
Regards,
Fedora Release Engineering
[1] https://fedorapeople.org/groups/schedule/f-41/f-41-key-tasks.html
[2] https://fedoraproject.org/wiki/Milestone_freezes
[3] https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process
[4] https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process
[5] https://qa.fedoraproject.org/blockerbugs/milestone/f41/final/buglist|
Please ensure that the reminder email is sent once the state becomes frozen. |
Want to help? Learn how to contribute to Fedora Docs ›