The Fedora 43 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 participants 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-43/f-43-key-tasks.html [2] https://fedoraproject.org/wiki/Fedora_43_Mass_Rebuild#Driving_Features
(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}
Metadata Update from @jnsamyak: - Issue tagged with: f43, high-gain, high-trouble, ops
Metadata Update from @jnsamyak: - Issue assigned to jnsamyak
CC: @amedvede @patrikp @kevin @humaton if you can do the reviews!
I reviewed all the open pr's linked above. :)
There were a few comments. The fedora-kiwi-descriptions pr seemed to be pointing to rawhide and not f43 branch?
It looks like "unpush rawhide-is-F43 bodhi updates that are stuck due to failed gating tests" is missing from the list - or is this no longer necessary, now that those updates could theoretically be pushed to stable with this fix present? Or would it still make sense to unpush, since maintainers need to actively do something to make the builds reach both rawhide and branched?
I don't remember doing it for the last release cycle, we cancelled the pending builds tho in koji, so I think this should be all good in my opinion. I don't think this is in the SOP or went to our retrospective as well. I don't think it makes sense to unncessary unpush these.
What are your thoughts? @kevin @adamwill @kparal @humaton
For koji outage, I have introduced a new script: https://pagure.io/releng/blob/main/f/scripts/branching/koji-http-toggle.sh
I don't think it makes sense to unncessary unpush these. What are your thoughts?
Sorry I have no idea :-)
However, I'd like to note that Adam prepared some branching SOP updates which he hoped would be included in the doc when the day comes, but they were not merged yet:
https://pagure.io/infra-docs-fpo/pull-request/386 https://pagure.io/infra-docs-fpo/pull-request/385
Can you please make sure the extra documented steps are also done during the branching procedure? Thanks a lot!
Thanks, I have these written in my notes too :D
Branching work will be discussed in releng matrix channel, and it will start in next 5 mins.
I don't remember doing it for the last release cycle
It was missed then ;) Which is why I'm asking ...
Latest fedora:43 container image seems to be F44 rawhide now. (same image as fedora:rawhide)
fedora:43
edit: okay I guess this is https://pagure.io/fedora-kiwi-descriptions/pull-request/206
this already went inn: https://pagure.io/fedora-kiwi-descriptions/c/e7b0e33446fe5407bc7dcc270380aab2a4c90079?branch=f43;
The retrospective has been formed for the same, notes are taken, the documentation are also updated to reflect the changes, so closing the issue.
Metadata Update from @jnsamyak: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)