bodhi: override status and mandatory_days_in_testing for EPEL bootstrap

Signed-off-by: Carl George <carlwgeorge@gmail.com>

roles/bodhi2/base/templates/production.ini.j2

@@ -648,6 +648,10 @@ f{{ FedoraRawhideNumber }}.pre_beta.critpath.stable_after_days_without_negative_
 eln.status = pre_beta
 eln.pre_beta.mandatory_days_in_testing = 0
 
+# EPEL bootstrap - During bootstrap updates don't require any days in testing.
+epel{{ EPELBootstrapNumber }}.status = pre_beta
+epel{{ EPELBootstrapNumber }}.pre_beta.mandatory_days_in_testing = 0
+
 
 ##
 ## Buildroot Override

vars/all/00-EPELCycleNumber.yaml

@@ -0,0 +1 @@
+EPELCycleNumber: 9

vars/all/EPELBootstrapNumber.yaml

@@ -0,0 +1 @@
+EPELBootstrapNumber: "{{ EPELCycleNumber|int + 1 }}.0"

vars/all/README-EPEL

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