Infrastructure/ansible
3
0
Fork 0
Code Issues Pull requests 6 Projects Releases Packages Wiki Activity Actions

vars: merge epel readme into readme for var substitution

Browse source 
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
This commit is contained in:
Kevin Fenzi 2024-07-31 15:53:22 -07:00
parent 45f5335356
commit 7437f37762
2 changed files with 29 additions and 28 deletions
Download patch file Download diff file Expand all files Collapse all files

29
vars/all/README
View file

@ -36,3 +36,32 @@ FedoraPreviousPreviousCycleNumber.yaml - number of previous previous stable rele
FedoraPreviousPrevious.yaml - true if there is a previous previous, otherwise false FedoraPreviousPrevious.yaml - true if there is a previous previous, otherwise false
FedoraRawhideNumber.yaml - The number of the current rawhide FedoraRawhideNumber.yaml - The number of the current rawhide
Frozen.yaml - If we are frozen or not, true or false 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

28
vars/all/README-EPEL
View file

@ -1,28 +0,0 @@
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 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