mirror of
https://pagure.io/fedora-infra/ansible.git
synced 2026-03-20 03:57:02 +08:00
79259c6911
This introduces a set of variables for managing infrastructure changes as EPEL minor versions change over time. This should drastically simplify our changes during EPEL mass branching. This also drops the earlier attempt of EPELCycleNumber and EPELBootstrapNumber variables, which are no longer used. Signed-off-by: Carl George <carlwgeorge@gmail.com>
54 lines
1.9 KiB
Plaintext
54 lines
1.9 KiB
Plaintext
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
|
|
|
|
|
|
The second set of these is to allow templates to handle the various stages of
|
|
EPEL minor versions so we don't have to remember all the places that need
|
|
changing. These only apply to EPEL 10 going forward, as previous major
|
|
versions didn't have minor versions.
|
|
|
|
There are several states that an EPEL minor version will move through.
|
|
|
|
* epel_minor: built from epelX branch against CentOS
|
|
* epel_branched_minor: built from epelX.Y branch against CentOS snapshot
|
|
* epel_z_minor: built from epelX.Y branch against RHEL
|
|
|
|
At any given time, we may have one, two, or three active minor version branches
|
|
for an EPEL major version. See the comments in EPEL.yaml for more details.
|