Skip to content
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

issue priorities. #3349

Merged
merged 3 commits into from
Mar 21, 2024
Merged

issue priorities. #3349

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
2af41f8
issue priorities.
shankarseal Mar 9, 2024
b38ced6
PR Feedback.
shankarseal Mar 15, 2024
7824454
clarification.
shankarseal Mar 19, 2024
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
10 changes: 10 additions & 0 deletions docs/Governance.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -115,6 +115,16 @@ Responsibilities:
* Manage github settings such as branch protection rules and repository secrets.
* Resolve any disputes among maintainers.

## Prioritizing Issues
shankarseal marked this conversation as resolved.
Show resolved Hide resolved

In the weekly triage meetings, new issues are assigned to collaborators and are set to a monthly milestone by which the issue is expected to be completed. It may not be possible for the assignees to address all the issues assigned to them by their target milestone. As a result issues may pile up in a given milestone. In such cases project admins can request that triage drivers and maintainers use *special labels* to prioritize issues as follows:
### P1:
This label represents highest priority. This label should be used for bugs impacting users, new feature or enhancements that are urgently requested by users. Collaborators should try to resolve these issues in the **current milestone**.
### P2:
This label is used for the next level of priority. Issues marked as P2 for the current milestone may be moved to the *next milestone* after discussing in the weekly triage meeting.
### P3:
This label is used for low priority issues. Issues marked with this label may be moved to the *next milestone* or the *backlog* milestone, without needing further discussion in the weekly triage meeting.

## Reviewing Pull Requests

Pull requests need at least two approvals before being eligible for merging.
Expand Down
Loading