On Thu, Mar 09, 2023 at 02:37:14PM +0100, Fabio Valentini wrote: > Hi all, > > As a follow-up from a recent discussion on Matrix/IRC, I'm proposing > the following change to the development cycle / release schedule: > > "Koji builds are blocked while mass branching and updates-testing > enablement are in progress." > > That's it, that's the entire RFC. Yeah, we have wanted to do this for a long time actually, but... The implemetation is tricky. As part of the branching process, after git repos and koji are switched, we have to commit and build fedora-repos/fedora-release in order for other builds to get the right disttag and to use the right repos. So, we need koji to let releng do that while blocking everyone else. ;( But that might be possible/doable now. (see below) Also, there's still going to be some corner cases I fear, like builds that were in progress before branching, or things that were stuck in ci/gating tests? Waiting for builds to finish is pretty time consuming. If someone started a gcc or libreoffice or chromium build it could be... a long time. I guess the way to be really sure would be: * set koji hub: ServerOffline = True OfflineMessage = Branching in progress, come back later LockOut = True (the comments for those is: ## If ServerOffline is True, the server will always report a ServerOffline fault (with ## OfflineMessage as the fault string). ## If LockOut is True, the server will report a ServerOffline fault for all non-admin ## requests. ) * Cancel all builds that are in progress. Maintainers can resubmit after the outage with the appropriate branches. * unpush all updates stuck in gating/pending? Is this too much? * do the branching steps, get everything in place, then open things on the hub. This is a lot more disruptive, but it's only for part of a day and I agree it's nicer to not have things to clean up. 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
