On Thu, Oct 18, 2018 at 3:05 PM Kevin Fenzi <kevin@xxxxxxxxx> wrote:
On 10/15/18 12:21 PM, Mohan Boddu wrote:
> Then I think we should use another variable (probably RelengFreeze)
> to indicate releng freeze, as they dont actually end on the same day.
> Also, we are using it for automated bodhi pushes, and we start
> pushing stable updates once we are a GO which we generally know
> on Thu itself. WDYT?
Yeah, more states. ;(
I wonder if we could look at aligning the infrastructure and releng
freezes. (Either by setting a new time like 15:00UTC to start both of
them, or by moving both to the same time). I know many people find
"00:00 UTC on tuesday" confusing. If we moved both to say 15:00UTC
tuesday it might work better?
+1 but what do you think of late UTC time on a Monday like 20:00 UTC?
As for pushing after GO, but before unfreeze, we could just do those
manually until freeze is up? At least the first one we need to watch
very carefully because it's the first set of packages going to the
'updates' repo instead of just being tagged in and getting composed on
the next night.
+1
If those don't work, we can of course add a RelengFreeze and a
MileStoneGo, but that means more things to modify.
kevin
_______________________________________________
infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
