Learn more about these different git repos.
Other Git URLs
The Fedora 40 schedule[1] has a mass branching schedule, We need to plan and coordinate all tasks in preparation for it. For the driving changes please refer to [2].
Most importantly for the reviewers or the participators for the PRs and other $stuff here is the checklist we created from our last branching and will be our source to check if we missed anything! https://docs.fedoraproject.org/en-US/infra/release_guide/mass_branching_checklist/
[1] https://fedorapeople.org/groups/schedule/f-40/f-40-key-tasks.html [2] https://fedoraproject.org/wiki/Fedora_40_Mass_Rebuild#Driving_Features
Metadata Update from @jnsamyak: - Issue tagged with: f40, high-gain, high-trouble
Metadata Update from @jnsamyak: - Issue assigned to jnsamyak
(for reviewers here is a checklist that one can copy this on the releng tracker, so we can keep track of everything needed in one place)
create-new-release-branches.py
--createfile
make-koji-release-tags
mass-branching-git.py
fedora:rawhide
fedora:${RAWHIDE}
As @sgallagh mentioned, before we start to branch:
(ELN) need to hit the pause button on our auto-rebuilds a few minutes ahead of the rest of the branch. So we can let anything in progress finish, do the final import to CentOS Stream 10, update our macros for RHEL 11, and then resume
ELN auto rebuilds are stopped
@decathorpe pointed out: https://bodhi.fedoraproject.org/updates/?search=fc40&releases=F41
Issues we hit:
Bodhi had some wrong info in it for f40/rawhide. See https://pagure.io/releng/issue/11950
we switched iot 'stable' to the new rawhide key, but it should stay on the previous/stable release. See: https://pagure.io/releng/issue/11951
the h264 repo was still pointing to f40... we need to make a empty repo for the new rawhide and point mirrormanager to it. I can provide a SOP for this.
we needed to run the playbooks/openshift-apps/toddlers.yml playbook to push out the change allowing users to request f40 branches. See https://pagure.io/releng/issue/11948
It would be nice to figure out a better way to stop users from submitting builds, but not sure what.
Overall much nicer than the last cycle IMHO. we have composes and everything is pretty much back to normal now. ;)
Thanks @kevin for these points! I'll make sure to update the sop+checklist as well from these details. Once, we have sop ready for [3] point, I can link that as well to our mass branching sop - we need to restructure the docs as well.
Sounds like a relief that i didn't mess much of the things <3
Thanks to you and @humaton!!!
Metadata Update from @jnsamyak: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.