On Sun, Apr 23, 2023 at 07:28:08AM +0000, Mattia Verga via devel wrote: > Isn't simpler to schedule: > > 1. lock down Koji in <branch_day - 24h> (stop accepting new builds, > possibly only for Rawhide) > 2. let Koji finish running builds (assuming there are none which > requires more than 24h) > 3. at <branch_day> check any stuck Rawhide update in Bodhi > 4. branch > 5. unlock Koji > > I think a 24h Koji outage is much clearer to users other than cancelling > their builds and unpushing their updates. Unless releng wants to take > note of those builds and updates and resubmit them after the mass > branching... well, 24hours is both too long and too short. On one hand we have some things that take longer than 24h sometimes. On the other we have a bunch of builds that only take a few minutes. I'd hate for a important update that only takes a few minutes to build to be delayed for 24hours. ;( I think we could perhaps look at resubmitting things. That could be a bit complex with targets and such, but it might be doable. kevin
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
