Adding preenable state to bodhi
This is used after branching and before bodhi enablement/beta freeze Signed-off-by: Mohan Boddu <mboddu@bhujji.com>
This commit is contained in:
parent
790922557b
commit
15ed96ff63
2 changed files with 10 additions and 3 deletions
|
@ -576,7 +576,10 @@ fedora_modular.mandatory_days_in_testing = 7
|
|||
# critpath number of admin approvals, and the critpath minimum karma. For example, if we want to set
|
||||
# Fedora 28 as a pre-beta, and we want it to have different rules in pre-beta and post-beta, we
|
||||
# could do something like this:
|
||||
{% if FedoraBranchedBodhi is defined and FedoraBranchedBodhi == 'prebeta' %}
|
||||
{% if FedoraBranchedBodhi is defined and FedoraBranchedBodhi == 'preenable' %}
|
||||
f{{ FedoraBranchedNumber }}.status = preenable
|
||||
f{{ FedoraBranchedNumber }}.pre_beta.mandatory_days_in_testing = 0
|
||||
{% elif FedoraBranchedBodhi is defined and FedoraBranchedBodhi == 'prebeta' %}
|
||||
f{{ FedoraBranchedNumber }}.status = pre_beta
|
||||
f{{ FedoraBranchedNumber }}.pre_beta.mandatory_days_in_testing = 3
|
||||
f{{ FedoraBranchedNumber }}.pre_beta.critpath.min_karma = 1
|
||||
|
|
|
@ -1,2 +1,6 @@
|
|||
#options are: prebeta, postbeta, current
|
||||
FedoraBranchedBodhi: prebeta
|
||||
# options are: preenable, prebeta, postbeta, current
|
||||
# preenable: After branching and before bodhi enablement/beta freeze
|
||||
# prebeta: After bodhi enablement/beta freeze and before beta release
|
||||
# postbeta: After beta release and before final release
|
||||
# current: After final release
|
||||
FedoraBranchedBodhi: preenable
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue