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

Update issues.md with modified priority definitions #6307

Merged
merged 2 commits into from
Apr 2, 2015
Merged

Update issues.md with modified priority definitions #6307

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a0e78df
Update issues.md
goltermann Apr 1, 2015
bdbe3fc
Update issues.md
goltermann Apr 1, 2015
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
14 changes: 6 additions & 8 deletions docs/devel/issues.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,14 +8,12 @@ Priorities

We will use GitHub issue labels for prioritization. The absence of a priority label means the bug has not been reviewed and prioritized yet.

Priorities are "moment in time" labels, and what is low priority today, could be high priority tomorrow, and vice versa. As we move to v1.0, we may decide certain bugs aren't actually needed yet, or that others really do need to be pulled in.

Here we define the priorities for up until v1.0. Once the Kubernetes project hits 1.0, we will revisit the scheme and update as appropriate.

Definitions
-----------
* P0 - something broken for users, build broken, or critical security issue. Someone must drop everything and work on it.
* P1 - must fix for earliest possible OSS binary release (every two weeks)
* P2 - must fix for v1.0 release - will block the release
* P3 - post v1.0
* untriaged - anything without a Priority/PX label will be considered untriaged
* P1 - must fix for earliest possible binary release (every two weeks)
* P2 - should be fixed in next major release version
* P3 - default priority for lower importance bugs that we still want to track and plan to fix at some point
* design - priority/design is for issues that are used to track design discussions
* support - priority/support is used for issues tracking user support requests
* untriaged - anything without a priority/X label will be considered untriaged