2014-12-02 03:07:46 +00:00
|
|
|
GitHub Issues for the Kubernetes Project
|
|
|
|
|
========================================
|
|
|
|
|
|
|
|
|
|
A list quick overview of how we will review and prioritize incoming issues at https://github.com/GoogleCloudPlatform/kubernetes/issues
|
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
Definitions
|
|
|
|
|
-----------
|
|
|
|
|
* P0 - something broken for users, build broken, or critical security issue. Someone must drop everything and work on it.
|
2015-04-01 20:00:37 +00:00
|
|
|
* P1 - must fix for earliest possible binary release (every two weeks)
|
2015-04-01 23:37:42 +00:00
|
|
|
* P2 - should be fixed in next major release version
|
2015-04-01 20:00:37 +00:00
|
|
|
* 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
|
2015-05-14 22:12:45 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
[]()
|
