Skip to content

Refine issue prioritization criteria in Governance.md #4667

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Refine issue prioritization criteria in Governance.md #4667

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 3 additions & 4 deletions docs/Governance.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -131,12 +131,11 @@ In the weekly triage meetings, new issues should be added to a milestone followi

To help prioritize issues, the triage drivers and maintainers MUST use *special labels* to prioritize issues as follows:
### P1:
This label represents highest priority. This label should be used for bugs impacting users, new features, or enhancements that are urgently
requested by users. `P1` issues MUST be set to the *current milestone*.
This label represents highest priority. This label should ONLY be applied to bugs or features with quantifiable business impact. Quantifiable business impact may include number of users, business blocked, or deployment blocked. Bugs with only qualitative impact (descriptions without numbers) will be ranked lower than quantifiable P1 bugs. `P1` issues MUST be set to the *current milestone*.
### P2:
This label is used for the next level of priority. Issues marked as `P2` can be set to the current milestone or to a future milestones (preferred).
This label is used for the next level of priority. Issues marked as `P2` will be set future milestones (preferred).
Copy link
Collaborator

@dthaler dthaler Sep 26, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change doesn't make sense to me. If there's already an open pull request (e.g. from a community member) and it's early in the month, what's the point of saying it "will" be set to a future milestone? I think this line should be kept as is.

### P3:
This label is used for low priority issues. Issues marked as `P3` can be set to any future milestone or the `Backlog` milestone.
This label is used for low priority issues. Issues marked as `P3` can be set to future milestones beyond 3 month or the `Backlog` milestone.

## Milestone Issues Limit
Triage managers need to ensure that the number of issues in a milestone does not exceed the capacity of the contributors
Expand Down
Loading