infra/ansible
24
5
Fork 48
Code Pull requests 14 Activity Actions
ansible/vars/all/FedoraBranchedBodhi.yaml

6 lines
273 B
YAML
Raw Permalink Normal View History

Simplify FedoraBranchedBodhi handling The current updates policy has the same rules for Branched after Beta freeze / updates-testing activation as for stable releases, so we don't need a specific Branched policy after that point at all. It only needs to exist for the 'preenable' state. The 'current' state is useless, so get rid of it. The Koji config handling was actually rather wrong in a few ways. If we ever got into a situation where FedoraBranched was true and FedoraBranchedBodhi was 'current', we'd allow block on the branch, which seems bad. Also, because this block wasn't conditionalized on FedoraBranched and FedoraBranchedNumber is 0 when FedoraBranched is false, we wound up defining a policy for tag 'f0', which is also dumb (but probably harmless). Getting rid of 'current' solves the first, conditionalizing the policy on FedoraBranched solves the second. Signed-off-by: Adam Williamson <awilliam@redhat.com>
2026-02-17 23:25:58 -08:00
# options are: preenable, prebeta, postbeta
Adding preenable state to bodhi This is used after branching and before bodhi enablement/beta freeze Signed-off-by: Mohan Boddu <mboddu@bhujji.com>
2020-08-13 21:05:23 -04:00
# 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
Fix majority of remaining yamllint warnings and errors Signed-off-by: Ryan Lerch <rlerch@redhat.com>
2024-11-27 13:48:08 +10:00
---
Fedora 44 Beta-1.2 is GO Signed-off-by: Samyak Jain <samyak.jn11@gmail.com>
2026-03-06 20:51:37 +05:30
FedoraBranchedBodhi: postbeta
Copy permalink