On Thu, Mar 9, 2023 at 3:28 PM Björn Persson <Bjorn@rombobjörn.se> wrote: > > What will packagers see? This is still up for discussion, I guess. And it will also depend on how this can be implemented. Ideally, "fedpkg build" would print a warning like "Mass branching is in progress, no builds can be submitted at this time.", but I'm not sure how hard that would be to implement. I think koji can already respond with something like an "there's an outage, try again later" error message, so it at least seems like it should be doable. > Will builds be queued, and get processed when the lock is released? No. Builds are doomed to be in the wrong state as soon as they are submitted during that time window (for example, "build was submitted when rawhide was still f38, but rawhide will be f39 once this build is finished"). The packager would need to retry to submit after releng has finished with their work (so, similar to how other infrastructure outages). > Will build attempts be rejected with a clear explanation? "You can't > build while we're branching. Please try again later." That would be nice, but I don't know how hard that would be to implement. > Or will packagers start asking why they get an incomprehensible stack > trace from fedpkg? Incomprehensible stack trace would be quite bad. Fabio _______________________________________________ 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
