mirror of
https://pagure.io/fedora-infra/ansible.git
synced 2026-05-01 05:51:56 +08:00
28fbce1a39
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>
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 we 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