88b6f9b6f3
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>
67 lines
1.9 KiB
Text
67 lines
1.9 KiB
Text
This directory contains variables (one per file) that are loaded into
|
|
various playbooks. The first set of these is to allow templates to
|
|
handle the various stages of Fedora development so we don't have to
|
|
remember all the places that need changing.
|
|
|
|
There's 3 states for Fedora releases:
|
|
|
|
1:
|
|
|
|
Rawhide N+1
|
|
Fedora N (stable)
|
|
Fedora N-1 (stable)
|
|
|
|
2: We branch a new release from rawhide:
|
|
|
|
Rahide N+2
|
|
Fedora N+1 (pre)
|
|
Fedora N (stable)
|
|
Fedora N-1 (stable)
|
|
|
|
3. That release is released:
|
|
|
|
Rawhide N+1
|
|
Fedora N (stable)
|
|
Fedora N-1 (stable)
|
|
Fedora N-2 (stable)
|
|
|
|
These are controlled by some variables:
|
|
|
|
00-FedoraCycleNumber.yaml - The current stable release
|
|
FedoraBranchedBodhi.yaml - If bodhi is enabled, whether it's preenable, prebeta, postbeta or current
|
|
FedoraBranchedNumber.yaml - The current branched release, or 0 if it doesnt exist
|
|
FedoraBranched.yaml - true if there is a branched, false otherwise
|
|
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 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
|
|
handle the various stages of EPEL development so we don't have to
|
|
remember all the places that need changing.
|
|
|
|
There's 3 states for EPEL releases:
|
|
|
|
1:
|
|
|
|
EPEL N (stable)
|
|
EPEL N-1 (stable)
|
|
|
|
2: We enable branch requests for a new release:
|
|
|
|
EPEL N+1 (bootstrap)
|
|
EPEL N (stable)
|
|
EPEL N-1 (stable)
|
|
|
|
3. That release is launched:
|
|
|
|
EPEL N (stable)
|
|
EPEL N-1 (stable)
|
|
EPEL N-2 (stable)
|
|
|
|
These are controlled by some variables:
|
|
|
|
00-EPELCycleNumber.yaml - The current stable release
|
|
EPELBootstrapNumber.yaml - The number of the bootstrap release
|