Fedora 43 Mass Branching Tracker

jnsamyak commented

2025-08-11 04:04:58 +00:00

Owner

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

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

jnsamyak commented

2025-08-11 04:06:46 +00:00

Author

Owner

T Day actions for mass branching

(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)

Merge all the preparatory PRs:

Merging and running ansible changes

Push the Changes

Commit, push, and apply the changes using the corresponding ansible playbooks for various services.

Disable Rawhide Builds in Koji

Configure an outage in Koji to disable Rawhide builds.
Cancel all running builds for Rawhide by listing and selecting relevant tasks, and then cancel each task.

PDC (Product Definition Center)

Create a new "product-release" in PDC using the provided script.
Clone or update the releng repository on PDC backend.
Run the create-new-release-branches.py script to set up the new release branches, ensuring to use the --createfile argument.

Koji

Run the make-koji-release-tags script from the releng repository to handle builds from the new branch.

Dist-Git

Create new branches in Git and update gitolite.conf to allow users to push to the new branches.
Run the mass-branching-git.py script to create new branches based on the file generated by PDC.

Bodhi

Link empty repos and create empty repos as necessary to prepare for the new release.
Create rawhide releases in Bodhi using appropriate commands for various types of releases (e.g., standard, container, flatpak).
Update MirrorManager to point to the new Rawhide release.
Enable autosigning on the Branched release after the compose is completed.
Perform ELN-related work, including updating image configurations and scripts.

Fedora Container Base Image

Import new images for Rawhide and update tags for fedora:rawhide and fedora:${RAWHIDE}.

Update Sync Script

Update the sync script in the releng repository with the new version.

Bugzilla version addition

Add 43 version to bugzilla

## T Day actions for mass branching (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) ### Merge all the preparatory PRs: - [ ] [pungi-fedora](https://pagure.io/pungi-fedora) - [ ] [fedora-kickstarts](https://pagure.io/fedora-kickstarts) - [ ] [fedora-comps](https://pagure.io/fedora-comps) - [ ] [workstation-ostree-config/](https://pagure.io/workstation-ostree-config/) - [ ] [fedora-release](https://src.fedoraproject.org/rpms/fedora-release) - [ ] [fedora-repos](https://src.fedoraproject.org/rpms/fedora-repos) - [ ] Toddlers ### Merging and running ansible changes #### Push the Changes - [ ] Commit, push, and apply the changes using the corresponding ansible playbooks for various services. ### Disable Rawhide Builds in Koji - [ ] Configure an outage in Koji to disable Rawhide builds. - [ ] Cancel all running builds for Rawhide by listing and selecting relevant tasks, and then cancel each task. ### PDC (Product Definition Center) - [ ] Create a new "product-release" in PDC using the provided script. - [ ] Clone or update the releng repository on PDC backend. - [ ] Run the `create-new-release-branches.py` script to set up the new release branches, ensuring to use the `--createfile` argument. ### Koji - [ ] Run the `make-koji-release-tags` script from the releng repository to handle builds from the new branch. ### Dist-Git - [ ] Create new branches in Git and update gitolite.conf to allow users to push to the new branches. - [ ] Run the `mass-branching-git.py` script to create new branches based on the file generated by PDC. ### Bodhi - [ ] Link empty repos and create empty repos as necessary to prepare for the new release. - [ ] Create rawhide releases in Bodhi using appropriate commands for various types of releases (e.g., standard, container, flatpak). - [ ] Update MirrorManager to point to the new Rawhide release. - [ ] Enable autosigning on the Branched release after the compose is completed. - [ ] Perform ELN-related work, including updating image configurations and scripts. ### Fedora Container Base Image - [ ] Import new images for Rawhide and update tags for `fedora:rawhide` and `fedora:${RAWHIDE}`. ### Update Sync Script - [ ] Update the sync script in the releng repository with the new version. ### Bugzilla version addition - [ ] Add 43 version to bugzilla

jnsamyak commented

2025-08-11 08:31:29 +00:00

Author

Owner

Metadata Update from @jnsamyak:

Issue tagged with: f43, high-gain, high-trouble, ops

**Metadata Update from @jnsamyak**: - Issue tagged with: f43, high-gain, high-trouble, ops

jnsamyak commented

2025-08-11 08:31:38 +00:00

Author

Owner

Metadata Update from @jnsamyak:

Issue assigned to jnsamyak

**Metadata Update from @jnsamyak**: - Issue assigned to jnsamyak

jnsamyak commented

2025-08-11 11:07:04 +00:00

Author

Owner

Repository	PR Link (Rawhide)	PR Link (F43)	Reviewed	Merged
pungi-fedora	Link to PR	Link to PR	❌	❌
fedora-kickstarts	Not required?	Link to PR	❌	❌
fedora-repos	Link to PR	Link to PR	❌	❌
fedora-release	Link to PR	Link to PR	❌	❌
workstation-os-config	Link to PR	Link to PR	❌	❌
fedora-lorax-template	Not required?	Just push a new branch without any changes?	❌	❌
fedora-kiwi-descriptions	No changes required?	Link to PR	❌	❌
fedora-comps	No changes required?	Link to PR	❌	❌
releng	No changes required!	No changes required, since the block retired is moved to poddlers and PDC is decomissioned!	❌	❌
ansible	No changes required?	Main Branch	❌	❌

| Repository | PR Link (Rawhide) | PR Link (F43) | Reviewed | Merged | |-------------------------------------|----------------------------------------------------------------------------------|-------------------------------------------------------------------------------|----------|--------| | pungi-fedora | [Link to PR](https://pagure.io/pungi-fedora/pull-request/1517) | [Link to PR](https://pagure.io/pungi-fedora/pull-request/1518) | ❌ | ❌ | | fedora-kickstarts | Not required? | [Link to PR](https://pagure.io/fedora-kickstarts/pull-request/1086) | ❌ | ❌ | | fedora-repos | [Link to PR](https://src.fedoraproject.org/rpms/fedora-repos/pull-request/160) | [Link to PR](https://src.fedoraproject.org/rpms/fedora-repos/pull-request/159)| ❌ | ❌ | | fedora-release | [Link to PR](https://src.fedoraproject.org/rpms/fedora-release/pull-request/387)| [Link to PR](https://src.fedoraproject.org/rpms/fedora-release/pull-request/388)| ❌ | ❌ | | workstation-os-config | [Link to PR](https://pagure.io/workstation-ostree-config/pull-request/660) | [Link to PR](https://pagure.io/workstation-ostree-config/pull-request/661) | ❌ | ❌ | | fedora-lorax-template | Not required? | Just push a new branch without any changes? | ❌ | ❌ | | fedora-kiwi-descriptions | No changes required? | [Link to PR](https://pagure.io/fedora-kiwi-descriptions/pull-request/205) | ❌ | ❌ | | fedora-comps | No changes required? | [Link to PR](https://pagure.io/fedora-comps/pull-request/1142) | :x: | ❌ | | releng | No changes required! | No changes required, since the block retired is moved to poddlers and PDC is decomissioned! | ❌ | ❌ | | ansible | No changes required? | [Main Branch](https://pagure.io/fedora-infra/ansible/pull-request/2788) | ❌ | ❌ |

jnsamyak commented

2025-08-11 13:28:28 +00:00

Author

Owner

CC: @amedvede @patrikp @kevin @humaton if you can do the reviews!

kevin commented

2025-08-11 18:57:12 +00:00

Owner

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?

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?

decathorpe commented

2025-08-12 10:38:33 +00:00

Contributor

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?

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](https://github.com/fedora-infra/bodhi/issues/5830) 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?

jnsamyak commented

2025-08-12 11:09:18 +00:00

Author

Owner

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

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

jnsamyak commented

2025-08-12 13:15:42 +00:00

Author

Owner

For koji outage, I have introduced a new script: https://pagure.io/releng/blob/main/f/scripts/branching/koji-http-toggle.sh

kparal commented

2025-08-12 13:32:04 +00:00

Contributor

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!

> 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!

jnsamyak commented

2025-08-12 13:36:02 +00:00

Author

Owner

Thanks, I have these written in my notes too :D

jnsamyak commented

2025-08-12 14:03:34 +00:00

Author

Owner

Branching work will be discussed in releng matrix channel, and it will start in next 5 mins.

decathorpe commented

2025-08-12 14:09:50 +00:00

Contributor

I don't remember doing it for the last release cycle

It was missed then ;) Which is why I'm asking ...

> I don't remember doing it for the last release cycle It was missed then ;) Which is why I'm asking ...

petersen commented

2025-08-13 04:50:45 +00:00

Latest fedora:43 container image seems to be F44 rawhide now.
(same image as fedora:rawhide)

edit: okay I guess this is https://pagure.io/fedora-kiwi-descriptions/pull-request/206

Latest `fedora:43` container image seems to be F44 rawhide now. (same image as `fedora:rawhide`) *edit:* okay I guess this is https://pagure.io/fedora-kiwi-descriptions/pull-request/206

jnsamyak commented

2025-08-13 05:11:02 +00:00

Author

Owner

this already went inn: https://pagure.io/fedora-kiwi-descriptions/c/e7b0e33446fe5407bc7dcc270380aab2a4c90079?branch=f43;