Fixing triage markdown as per #3382

This commit is contained in:
Tom Lant 2017-03-09 12:00:54 +00:00 committed by Matthew Hodgson
parent 271fedd1e9
commit 927d305ed9
1 changed files with 20 additions and 13 deletions

View File

@ -267,21 +267,28 @@ Triaging issues
Issues will be triaged by the core team using the following primary set of tags: Issues will be triaged by the core team using the following primary set of tags:
priority: priority:
P1: top priority; typically blocks releases.
P2: one below that * P1: top priority; typically blocks releases
P3: non-urgent * P2: still need to fix, but lower than P1
P4/P5: bluesky some day, who knows. * P3: non-urgent
* P4: intereseting idea - bluesky some day
* P5: recorded for posterity/to avoid duplicates. No intention to resolves right now.
bug or feature: bug or feature:
* bug
* feature
bug severity: bug severity:
* cosmetic - feature works functionally but UI/UX is broken.
* cosmetic - feature works functionally but UI/UX is broken
* critical - whole app doesn't work * critical - whole app doesn't work
* major - entire feature doesn't work * major - entire feature doesn't work
* minor - partially broken feature (but still usable) * minor - partially broken feature (but still usable)
additional categories:
* release blocker * release blocker
* ui/ux (think of this as cosmetic) * ui/ux (think of this as cosmetic)
* network (specific to network conditions) * network (specific to network conditions)
* platform (platform specific) * platform (platform specific)