Clarify the Frozen variable

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>
This commit is contained in:
Adam Williamson 2025-02-18 09:10:26 -08:00 committed by kevin
parent 2e3eaabb1c
commit 88b6f9b6f3
3 changed files with 8 additions and 3 deletions

View file

@ -35,7 +35,7 @@ FedoraPreviousCycleNumber.yaml - number of previous stable release
FedoraPreviousPreviousCycleNumber.yaml - number of previous previous stable release or 0
FedoraPreviousPrevious.yaml - true if there is a previous previous, otherwise false
FedoraRawhideNumber.yaml - The number of the current rawhide
Frozen.yaml - If we are frozen or not, true or false
Frozen.yaml - If infra (InfraFrozen) and the pending release (NextReleaseFrozen) are frozen or not, true or false
This directory also contains variables (one per file) that are loaded into
various playbooks. The first set of these is to allow templates to