Clarify the Frozen variable #2481
No reviewers
Labels
No labels
freeze-break-request
post-freeze
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Infrastructure/ansible#2481
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "clarify-frozen"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Per https://pagure.io/infra-docs-fpo/pull-request/361 there seems
to be substantial confusion about what the "Frozen" variable
means: does it refer to the infrastructure freeze, or a freeze
for the pending release? It seems like @kevin thought about it
as referring to the former, but the only practical use of it in
this repo treats it as the latter.
Let's make this clear with explicitly-named variables.
InfraFrozen tracks the infrastructure freeze, NextReleaseFrozen
tracks freezes for the pending release. We formerly had a var
called RelEngFrozen which had a similar meaning, but I like this
name more because the freeze doesn't apply to all releng
operations - just because the current Branched is frozen doesn't
mean Rawhide or stable releases are frozen.
We keep Frozen for 'backwards compatibility', in case anyone is
referring to this variable from outside of the repo.
This goes along with https://pagure.io/infra-docs-fpo/pull-request/361
which updates the SOPs.
Signed-off-by: Adam Williamson awilliam@redhat.com
Build succeeded.
https://fedora.softwarefactory-project.io/zuul/buildset/c3a49edf44e044c58a2ba54cadad230b
rebased onto
2e3eaabb1c
rebased onto
2e3eaabb1c
Build succeeded.
https://fedora.softwarefactory-project.io/zuul/buildset/1d357f93fba441f88c5a8a50d228a063
I agree with changing the name, that seems fine and more descriptive.
Pull-Request has been merged by kevin