kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update issues.md 

Updating priority definitions - open for discussion if there are other opinions.
This commit is contained in:
goltermann 2015-04-01 13:00:37 -07:00
parent 5ed385b9e7
commit fcd666c840
1 changed files with 6 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
issues.md
View File

@ -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 relase 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