Commit graph

5 commits

Author SHA1 Message Date
Adam Williamson
88b6f9b6f3 Clarify the Frozen variable
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>
2025-02-18 19:51:50 +00:00
Adam Williamson
91267d4d49 Templatize branched nightly cron
Instead of doing this by hand at branch and final release, let's
make it a template.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-11-27 10:08:06 -08:00
Kevin Fenzi
7437f37762 vars: merge epel readme into readme for var substitution
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
2024-07-31 15:53:22 -07:00
Kevin Fenzi
65f2e53b3a Drop a unused file, update readme. 2018-10-01 21:57:27 +00:00
Kevin Fenzi
bf771767ef Test out a little bit of variable stuff to see if it will work to help us. 2018-10-01 20:45:05 +00:00