github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-08-11 13:02:14 +00:00
Code Issues Projects Releases Wiki Activity

Formalize the meanings of issue priority labels.

Browse Source
This commit is contained in:
Quinton Hoole 2015-12-16 08:45:08 -08:00
parent 3415f1dfc2
commit 12d1f2344f
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/proposals/issue-priorities.md Normal file
View File

@ -0,0 +1,6 @@
These are the meanings of the labels priority/p0 ... priority/p3 that we apply to issues in order to try to prioritize them relative to each other. We try to apply these priority labels consistently across the entire project, but if you notice an issue that you believe to be misprioritized, please do let us know and we will evaluate your counter-proposal.
- **priority/P0**: Must be actively worked on as someone's top priority right now. Stuff is burning. If it's not being actively worked on, someone is expected to drop what they're doing immediately to work on it. TL's of teams responsible for making sure that all P0's in their area are being actively worked on.
- **priority/P1**: Should be staffed and worked on either currently, or very soon, ideally in time for the next release.
- **priority/P2**: Agreed that this would be good to have, but we possibly don't have anyone available to work on it right now or in the immediate future. Hopefully in the future some time we will. Community contributions would be most welcome in the mean time.
-**priority/P3**: Probably useful, but not yet enough support to actually get it done. These are mostly place-holders for potentially good ideas, so that they don't get completely forgotten, and can be referenced/deduped every time they come up.