infra/docs
18
1
Fork 15
Code Issues 55 Pull requests 6 Projects Releases Packages Wiki Activity Actions

openQA sysadmin guide branching: rewrite with improvements #490

Merged
kevin merged 1 commit from adamwill/infra-docs:openqa-sysadmin-branch-workarounds into main 2026-02-23 17:34:56 +00:00
Conversation 3 Commits 1 Files changed 1 +96 -83
adamwill commented 2026-02-06 20:29:34 +00:00
Member
Copy link

Complete rewrite of the openQA guide section on handling the
mass branching process. This splits it into sections to avoid it
being a long shaggy hard-to-read blob, and tries to make things
much more concrete and step-by-step based on experience from the
last two cycles.

Signed-off-by: Adam Williamson awilliam@redhat.com

Complete rewrite of the openQA guide section on handling the mass branching process. This splits it into sections to avoid it being a long shaggy hard-to-read blob, and tries to make things much more concrete and step-by-step based on experience from the last two cycles. Signed-off-by: Adam Williamson <awilliam@redhat.com>
Mention that the %workarounds matrix must be updated for the new
Rawhide number, and mention that multiple version ident needles
need to be updated.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
adamwill force-pushed openqa-sysadmin-branch-workarounds from e914b51612 to 744b675491 2026-02-07 19:18:45 +00:00 Compare
adamwill changed title from openQA sysadmin guide: couple of branching guide updates to openQA sysadmin guide branching: rewrite with improvements 2026-02-07 19:19:22 +00:00
ryanlerch force-pushed openqa-sysadmin-branch-workarounds from 744b675491 to aef9f56859
All checks were successful
/ test (pull_request) Successful in 18s
Details
2026-02-23 10:27:03 +00:00 Compare
ryanlerch commented 2026-02-23 10:36:59 +00:00
Owner
Copy link

Apologies -- i rebased this branch as I added CI checking to the docs build.

Apologies -- i rebased this branch as I added CI checking to the docs build.
adamwill commented 2026-02-23 17:08:31 +00:00
Author
Member
Copy link

No problem, I just wish someone would merge it. :D

No problem, I just wish someone would merge it. :D
kevin merged commit aef9f56859 into main 2026-02-23 17:34:56 +00:00
adamwill commented 2026-02-23 17:39:59 +00:00
Author
Member
Copy link

much rejoicing

*much rejoicing*
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
obsolete

SOPs or howtos that are obsolete and should be removed.

  
rerwite-required

   
SOP

   
untriaged
  
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
obsolete
rerwite-required
SOP
untriaged
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
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
infra/docs!490
No description provided.