Learn more about these different git repos.
Other Git URLs
This was discussed on the mailing list, and it seems to be doable (by blocking things in the koji hub with an outage message, or something like that): https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/GWY4TIDIP65HA2V33F2ROU2MJLKMRZ7E/#GWY4TIDIP65HA2V33F2ROU2MJLKMRZ7E
Would it be possible to do something like this for the upcoming mass branching? The release cycle is already chaotic enough due to $DECISIONS, I would rather avoid having to deal with builds that are stuck in inconsistent states (especially because GNOME 45 beta will land over the next few days).
Before the next mass branching would be great.
N/A
Builds that get submitted during the mass branching have a good chance of ending up in weird and inconsistent states, needing manual fixes from releng or even release-bumps+rebuilds.
I knew we are forgetting something! Thanks for bringing this up here is a draft of the announcement:
Hi All, Fedora Linux 39 is going to be branched from rawhide on 2023-08-08 at 10:30 UTC as per the previous discussion[1] we are going to disable new koji builds for the duration of this event. All builds that will be running at that time for the rawhide will be canceled and can be resubmitted by maintainers after the branching. All rawhide updates that are in a pending state for rawhide will be unpushed. Once Fedora Linux 40 is branched we will reenable builds in koji. 1 - https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/GWY4TIDIP65HA2V33F2ROU2MJLKMRZ7E/#GWY4TIDIP65HA2V33F2ROU2MJLKMRZ7E
We need to update the branching SOP and create a new mail template in the releng repo so this is copy/paste operation next time.
Metadata Update from @humaton: - Issue tagged with: high-gain, medium-trouble, ops
Shouldn't this be Fedora Linux 39 for this branch and the Fedora 40 would be in Jan/Feb next year?
Metadata Update from @smooge: - Issue untagged with: high-gain, medium-trouble, ops
updated thanks @smooge.
Looks good to me. Thank you! I actually meant to file a ticket for this earlier, but forgot about it :(
Looks ok to me too.
Hello, branching is done and we disabled the builds during the event, canceled all the builds, and reenabled them again.
As it turns out we were not able to disable only the build on rawhide, so we disabled the whole build system for a few hours. I am not sure if this is the way forward. Maybe it is and we just need to communicate it better.
Even when we have disabled koji somehow few builds end up in a weird state.
There was a proposal on the mailing list by somebody to block all packages on rawhide tag and unblock them afterward. This solution will be surgical only for rawhide but a really big hammer in another way and that is mass changes on all packages in the rawhide branch.
Log in to comment on this ticket.