we are now in the infrastructure freeze leading up to the Fedora 44
Beta release. This is a pre release freeze.
We do this to ensure that our infrastructure is stable and ready to
release Fedora 44 Beta when it's available.
You can always check if an infrastructure freeze is in place by
checking the value of the InfraFrozen variable at:
https://forge.fedoraproject.org/infra/ansible/src/branch/main/vars/all/Frozen.yaml
You can see a list of hosts that do not freeze by checking out the
ansible repo and running the freezelist script:
git clone
https://forge.fedoraproject.org/infra/ansible/src/branch/main/vars/all/Frozen.yaml
ansible/scripts/freezelist -i inventory
Any host listed as "freezes" is frozen until 2026-03-10 (or later if
release slips). Frozen hosts should have no changes made to them without
a sign-off on the change from at least 2 sysadmin-main or rel-eng
members, along with (in most cases) a patch of the exact change to be
made to this list and/or a pull-request to the infra/ansible repo.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
Per https://pagure.io/infra-docs-fpo/pull-request/361 there seems
to be substantial confusion about what the "Frozen" variable
means: does it refer to the infrastructure freeze, or a freeze
for the pending release? It seems like @kevin thought about it
as referring to the former, but the only practical use of it in
this repo treats it as the latter.
Let's make this clear with explicitly-named variables.
InfraFrozen tracks the infrastructure freeze, NextReleaseFrozen
tracks freezes for the pending release. We formerly had a var
called RelEngFrozen which had a similar meaning, but I like this
name more because the freeze doesn't apply to *all* releng
operations - just because the current Branched is frozen doesn't
mean Rawhide or stable releases are frozen.
We keep Frozen for 'backwards compatibility', in case anyone is
referring to this variable from outside of the repo.
This goes along with https://pagure.io/infra-docs-fpo/pull-request/361
which updates the SOPs.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
It seems this has been set true ever since F41 Final freeze. It
probably should have been set false after F41 shipped, but we
missed it.
We did freeze for F42 branching, but I'm pretty sure we declared
that over now. Next freeze is on Feb 18, for Beta.
Also, the RelEngFrozen variable is no longer used by anything.
It was only ever used for one thing in Bodhi config, but that
use was removed in 02cdf36 . So let's get rid of the variable.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
