Infrastructure/infra-docs-fpo
3
0
Fork 0
Code Issues 100 Pull requests 6 Projects Releases Packages Wiki Activity Actions

openQA and branching SOP changes related to openQA at branch time #360

Open
adamwill wants to merge 1 commit from openqa-update into master
pull from: openqa-update
merge into: Infrastructure:master
Conversation 3 Commits 1 Files changed 2 +215 -13
adamwill commented 2025-02-10 20:20:55 +00:00
Contributor
Copy link

This is a big update that's mainly about documenting all the tasks
related to openQA at branch time. We also add a couple of bits to
the releng SOP: one noting that co-ordination with quality and CI
folks is needed during branching, and one to get the fedfind
release metadata updated, which is a critical step that should
happen during branching. Currently I Just Know that this has to
happen, but we should write it down. This metadata file is not
templated in Ansible because that would cause it to be updated too
soon at release time (we need fedfind's stable release list to
change only when the new release is available in the mirror
system, for...reasons).

This also documents how we handle openQA needles, since I noticed
while writing the branching steps that it's not written down, and
drops the section about autocloudreporter as that's obsolete and
no longer used.

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

This is a big update that's mainly about documenting all the tasks related to openQA at branch time. We also add a couple of bits to the releng SOP: one noting that co-ordination with quality and CI folks is needed during branching, and one to get the fedfind release metadata updated, which is a critical step that should happen during branching. Currently I Just Know that this has to happen, but we should write it down. This metadata file is not templated in Ansible because that would cause it to be updated too soon at release time (we need fedfind's stable release list to change only when the new release is available in the mirror system, for...reasons). This also documents how we handle openQA needles, since I noticed while writing the branching steps that it's not written down, and drops the section about autocloudreporter as that's obsolete and no longer used. Signed-off-by: Adam Williamson <awilliam@redhat.com>
zlopez commented 2025-02-11 11:24:14 +00:00
Contributor
Copy link

@jnsamyak Could you check this out?

@jnsamyak Could you check this out?
kevin commented 2025-02-13 16:49:02 +00:00
Contributor
Copy link

FWIW, it looks fine to me. We can always refine it more after pushing it.

FWIW, it looks fine to me. We can always refine it more after pushing it.
zlopez commented 2025-03-28 13:47:09 +00:00
Contributor
Copy link

This now has conflicts when trying to merge it.

This now has conflicts when trying to merge it.
This pull request is broken due to missing fork information.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin openqa-update:openqa-update
git checkout openqa-update

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git checkout master
git merge --no-ff openqa-update
git checkout openqa-update
git rebase master
git checkout master
git merge --ff-only openqa-update
git checkout openqa-update
git rebase master
git checkout master
git merge --no-ff openqa-update
git checkout master
git merge --squash openqa-update
git checkout master
git merge --ff-only openqa-update
git checkout master
git merge openqa-update
git push origin master
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
rerwite-required

   
SOP

   
untriaged
  
blocked

Indicates the work cannot proceed. There is a dependency or an issue that is preventing the team from completing the task. This is a flag for the Scrum Master to help unblock the team.

  
Bug

The software is not behaving as expected. It could be an error, a crash, or an incorrect result. Bugs often need to be prioritized based on their severity and business impact

  
Chore

Tasks that are necessary but don't directly deliver new value to the end-user. These are internal tasks like updating a library, managing user accounts, or setting up a new service.

  
Feature

It's something that a user would be able to see or interact with, such as a new button, a new page, or an improved workflow.

  
in-progress

This label is for work that a developer is actively working on. This is usually what you'll see on the "In Progress" column of your project board.

  
points:1

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: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.

  
points:2

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:3

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:5

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:8

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.

  
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.

  
ready

indicates that an issue has been fully refined, has a story point value, and is ready to be pulled into a sprint. It has all the information needed for a developer to start working on it immediately.

  
review

This indicates that the work is complete, but it is now in a review state. This could mean a peer code review, a QA check, or a review by the Product Owner.

  
Technical Debt

work that improves the codebase without adding new features. It's work that pays down the "debt" you've accumulated, such as refactoring a messy piece of code, improving test coverage.

No labels
rerwite-required
SOP
untriaged
blocked
Bug
Chore
Feature
in-progress
points:1
points:13
points:2
points:3
points:5
points:8
priority:high
priority:low
priority:medium
ready
review
Technical Debt
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
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.

Dependencies

No dependencies set.

Reference: Infrastructure/infra-docs-fpo#360
No description provided.
Delete branch "openqa-update"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?