releng/tickets
10
2
Fork 1
Code Issues 103 Pull requests Projects Releases Packages Wiki Activity Actions

F44 Mass Branching: Preparatory PRs #13192

New issue
Closed
opened 2026-01-29 11:31:43 +00:00 by patrikp · 3 comments
patrikp commented 2026-01-29 11:31:43 +00:00
Member
Copy link
Repository PR link: Rawhide PR link: F44 Reviewed Merged Notes
pungi-fedora Link Link ✅ ✅ The branch for the F44 should NOT have had the branch changed to f44, it should remain main because fedora-comps only has one branch (main).
fedora-kickstarts N/A N/A N/A N/A This seems to be retired and completely replaced by KIWI.
fedora-kiwi-descriptions N/A Link ✅ ✅
fedora-comps Link N/A ✅ ✅
fedora-lorax-templates N/A N/A N/A N/A All that was needed here was to create and push a new branch without any changes.
workstation-ostree-config Link Link ✅ ✅
fedora-release Link Link ✅ ✅
fedora-repos Link Link ✅ ✅
statusfpo Link N/A ✅ ✅
ansible N/A Link ✅ ✅
| Repository | PR link: Rawhide | PR link: F44 | Reviewed | Merged | Notes | |----------------------------|------------------|-------------|-----------|----------|-------| | `pungi-fedora` | [Link](https://forge.fedoraproject.org/releng/pungi-fedora/pulls/1599) | [Link](https://forge.fedoraproject.org/releng/pungi-fedora/pulls/1600) | ✅ | ✅ | The branch for the F44 should NOT have had the branch changed to `f44`, it should remain `main` because `fedora-comps` only has one branch (`main`). | `fedora-kickstarts` | **N/A** | **N/A** | **N/A** | **N/A** | This seems to be retired and completely replaced by KIWI. | | `fedora-kiwi-descriptions` | **N/A** | [Link](https://pagure.io/fedora-kiwi-descriptions/pull-request/261) | ✅ | ✅ | | `fedora-comps` | [Link](https://pagure.io/fedora-comps/pull-request/1238) | **N/A** | ✅ | ✅ | | `fedora-lorax-templates` | **N/A** | **N/A** | **N/A** | **N/A** | All that was needed here was to create and push a new branch without any changes. | `workstation-ostree-config`| [Link](https://pagure.io/workstation-ostree-config/pull-request/729) | [Link](https://pagure.io/workstation-ostree-config/pull-request/730) | ✅ | ✅ | | `fedora-release` | [Link](https://src.fedoraproject.org/rpms/fedora-release/pull-request/396) | [Link](https://src.fedoraproject.org/rpms/fedora-release/pull-request/397) | ✅ | ✅ | | `fedora-repos` | [Link](https://src.fedoraproject.org/rpms/fedora-repos/pull-request/162) | [Link](https://src.fedoraproject.org/rpms/fedora-repos/pull-request/163) | ✅ | ✅ | | `statusfpo` | [Link](https://github.com/fedora-infra/statusfpo/pull/78) | **N/A** | ✅ | ✅ | | `ansible` | **N/A** | [Link](https://pagure.io/fedora-infra/ansible/pull-request/3079) | ✅ | ✅ |
patrikp self-assigned this 2026-01-29 11:31:43 +00:00
patrikp changed title from Fedora 44 Mass Branching: Preparatory PRs to F44 Mass Branching: Preparatory PRs 2026-01-29 11:41:05 +00:00
patrikp commented 2026-01-30 14:59:12 +00:00
Author
Member
Copy link

I think this is ready for review now.
@jnsamyak @kevin @amedvede

For reference, here are the historical trackers.
F43 Mass Branching: #12870
F42 Mass Branching: #12550

I think this is ready for review now. @jnsamyak @kevin @amedvede For reference, here are the historical trackers. F43 Mass Branching: https://forge.fedoraproject.org/releng/tickets/issues/12870 F42 Mass Branching: https://forge.fedoraproject.org/releng/tickets/issues/12550
amedvede commented 2026-02-03 18:24:47 +00:00
Member
Copy link

I reviewed PRs:
pungi-fedora - looks good
fedora-kickstarts - correct, it was retired from f44
fedora-kiwi-description - looks good just need to update readme acording to past mass branching
fedora-comps - looks good
fedora-lorax-templates - right
workstation-ostree-config - looks good
fedora-release - looks good
fedora-repos - looks good only f46 key is missing
releng/tooling - acording to SOP there few things needs to be changed
ansible - looks good
statusfpo - missing in SOP doc

I reviewed PRs: `pungi-fedora` - looks good `fedora-kickstarts` - correct, it was retired from `f44` `fedora-kiwi-description` - looks good just need to update readme acording to past mass branching `fedora-comps` - looks good `fedora-lorax-templates` - right `workstation-ostree-config` - looks good `fedora-release` - looks good `fedora-repos` - looks good only f46 key is missing `releng/tooling` - acording to SOP there few things needs to be [changed](https://docs.fedoraproject.org/en-US/infra/release_guide/sop_mass_branching/#_key_changes) `ansible` - looks good `statusfpo` - missing in SOP doc
jnsamyak commented 2026-02-09 05:43:26 +00:00
Owner
Copy link

Close this one in liew of mass branching getting over.

Close this one in liew of mass branching getting over.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
modular-tags-at-branchtime
product-release
createrepoc
bz-epel
branch-eol-sop
multiline-sop
weird-loop
container-branching
unretire
blocking-for-f27
json-json-json
orphan-management
find-failures-owners
cvsadmin
twoweek-stable
rawhide-stable
Labels
Clear labels   
after freeze

   
automation

   
backlog

Tasks that will take longer then ~4 hours to do

  
blocked

   
change-ack

Changes that have releng work and are accepted

  
change-nak

Changes that have releng work and have been rejected

  
change-noreleng

Changes that do not have any releng work

  
changes
  
Closed As
Can't Fix
Closed with the reason of Can't Fix

  
Closed As
Duplicate
Closed with the reason of Duplicate

  
Closed As
Fixed
Closed with the reason of Fixed

  
Closed As
Fixed with Explanation
Closed with the reason of Fixed with Explanation

  
Closed As
Get back later
Closed with the reason of Get back later

  
Closed As
Grooming
Closed with the reason of Grooming

  
Closed As
Insufficient data
Closed with the reason of Insufficient data

  
Closed As
Invalid
Closed with the reason of Invalid

  
Closed As
It's all good
Closed with the reason of It's all good

  
Closed As
taiga
Closed with the reason of taiga

  
Closed As
upstream
Closed with the reason of upstream

  
dev

   
docs

   
easyfix

   
epel

   
f26

   
f27

Fedora 27

  
f28

Fedora 28

  
f29

Fedora 29

  
f30

   
f31

   
f32

   
f33

Fedora 33

  
f34

   
f35

Fedora 35

  
f36

   
f37

   
f38

   
f39

Fedora 39

  
f40

   
f41

Fedora 41

  
f42

Fedora 42

  
f43

Fedora 43

  
f44

Fedora 44

  
f45

Fedora 45

  
fedora

   
groomed

   
high-gain

   
high-trouble

   
in-progress

   
in-review

   
investigation

   
legal

   
low-gain

   
low-trouble

   
mass rebuild

   
medium-gain

   
medium-trouble

   
meeting

   
mini-initiative

   
new_artifact

New artifact for fedora release

  
ops

   
pdc_retirement

   
rawhide

   
RCA

Root cause analysis

  
review

   
script

   
sidetarget

   
sprint-0

   
sprint-1

Releng Sprint 1 Tracker

  
sprint-2

Sprint 2

  
sprint-3

Releng Sprint 3 Tracker

  
sprint-4

RelEng Spring 4 Tracker

  
sprint-5

RelEng Sprint Tracker 5 (Nov 18 - Dec 02)

  
unfrozen

Revisit after freeze

  
waiting on external
  
Backlog Status
Needs Review
Work items that have been created or updated but need review, refinement, or approval before they can be considered ready for sprint planning.

  
Backlog Status
Ready
Work items that have been reviewed, refined, and are ready to be committed to a sprint. These items have clear requirements and can be worked on immediately when capacity is available.

  
chore

Work that needs to be done but doesn't add new functionality or fix bugs. Maintenance tasks that keep the system running smoothly and the codebase clean.

  
documentation

Work focused on creating, updating, or improving documentation for users, developers, or system administrators.

  
points
01
A task that is simple, small, and has very little uncertainty. It should be easy enough for any team member to pick up and complete quickly, without a lot of discussion or research.

  
points
02
This is a task that is slightly more complex or larger than a "1." It might involve two or three simple steps, but the outcome is still very clear and there's little uncertainty.

  
points
03
Medium-sized task with some noticeable complexity. It might require a bit more thought or collaboration. The steps are well-defined, but it's not a trivial change.

  
points
05
A significant piece of work. It has more complexity and a higher degree of uncertainty than smaller tasks. It might require some research, a design discussion, or collaboration across multiple teams.

  
points
08
Complex task with a lot of uncertainty. It's often the largest size that a team will consider for a single sprint. It likely requires a detailed breakdown and multiple team members to complete.

  
points
13
Any task that feels like it's a "13" or more is considered an Epic. These are too large and uncertain to be worked on in a single sprint and should be broken down.

  
Priority
High
This is for work that is critical and needs to be addressed in the next sprint. It's often for urgent bugs, important features, or a major piece of technical debt that is blocking other work.

  
Priority
Low
This is for work that is good to do but not urgent. It's a candidate for being worked on when there's extra time or when it rises in importance. It can stay in the backlog for a longer period.

  
Priority
Medium
This is for important work that should be done soon, but isn't as urgent as a high-priority item. It will likely be considered for the next 1-2 sprints.

  
Sprint Status
Blocked
Work items that cannot progress due to external dependencies, blockers, or issues that need resolution.

  
Sprint Status
Done
Work items that have been completed, reviewed, and integrated. No further work is needed within the current sprint.

  
Sprint Status
In Progress
Work items currently being worked on by a team member. Active development, research, or implementation is happening.

  
Sprint Status
Review
Work items that are complete but need review, testing, or approval before being marked as done.

  
Sprint Status
To Do
Work items that are committed to the sprint but haven't been started yet. These items are ready to be picked up by team members.

  
Technical Debt

Work that addresses shortcuts, workarounds, or suboptimal implementations that were done previously to meet deadlines. These items improve code quality, maintainability, or performance without adding new features.

  
Work Item
Bug
Issues where the system is not working as intended or designed. Bugs represent deviations from expected behavior.

  
Work Item
Epic
Large initiatives that are broken down into multiple smaller work items (user stories, tasks, bugs). Epics represent significant features or projects that span multiple sprints.

  
Work Item
Spike
Time-boxed research, investigation, or proof-of-concept work to reduce uncertainty or explore solutions. Spikes help inform future development decisions.

  
Work Item
Task
Used to break down larger user stories into smaller, manageable implementation pieces. They focus on the specific technical steps needed to deliver the user story's value.

  
Work Item
User Story
User-facing features or functionality that can be framed from a user perspective, describing what someone wants to accomplish and why.

No labels
after freeze
automation
backlog
blocked
change-ack
change-nak
change-noreleng
changes
Closed As
Can't Fix
Closed As
Duplicate
Closed As
Fixed
Closed As
Fixed with Explanation
Closed As
Get back later
Closed As
Grooming
Closed As
Insufficient data
Closed As
Invalid
Closed As
It's all good
Closed As
taiga
Closed As
upstream
dev
docs
easyfix
epel
f26
f27
f28
f29
f30
f31
f32
f33
f34
f35
f36
f37
f38
f39
f40
f41
f42
f43
f44
f45
fedora
groomed
high-gain
high-trouble
in-progress
in-review
investigation
legal
low-gain
low-trouble
mass rebuild
medium-gain
medium-trouble
meeting
mini-initiative
new_artifact
ops
pdc_retirement
rawhide
RCA
review
script
sidetarget
sprint-0
sprint-1
sprint-2
sprint-3
sprint-4
sprint-5
unfrozen
waiting on external
Backlog Status
Needs Review
Backlog Status
Ready
chore
documentation
points
01
points
02
points
03
points
05
points
08
points
13
Priority
High
Priority
Low
Priority
Medium
Sprint Status
Blocked
Sprint Status
Done
Sprint Status
In Progress
Sprint Status
Review
Sprint Status
To Do
Technical Debt
Work Item
Bug
Work Item
Epic
Work Item
Spike
Work Item
Task
Work Item
User Story
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Sprint ( 2026-01-26 to 2026-02-08 )
Assignees
Clear assignees
No assignees
patrikp
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks
#13185 F44 Mass Branching Tracker
releng/tickets
Reference
releng/tickets#13192
No description provided.