honeymoose
/
angular-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

refactor(dev-infra): Update triage labels documentation (#38081) 

Add new type: confusing and type: use-case labels to the triage readme as well
as clarify that freq and severity are only required for type: bug/fix

PR Close #38081
This commit is contained in:
Andrew Scott 2020-07-20 09:28:08 -07:00 committed by Andrew Kushnir
parent 9dc5e8e7e2
commit c8c74153b1
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/TRIAGE_AND_LABELS.md
View File

@ -62,6 +62,8 @@ What kind of problem is this?
* `type: feature`
* `type: performance`
* `type: refactor`
* `type: use-case`
* `type: confusing`
## Caretaker Triage Process (Primary Triage)
@ -83,8 +85,8 @@ Once the primary triage is done, the ng-bot automatically adds the milestone `ne
The component owner is responsible for assigning one of the labels from each of these categories to the issues that have the milestone `needsTriage`:
- `type: *`
- `frequency: *`
- `severity: *`
- `frequency: *` (only required for `type: bug/fix`)
- `severity: *` (only required for `type: bug/fix`)
We've adopted the issue categorization based on [user pain](http://www.lostgarden.com/2008/05/improving-bug-triage-with-user-pain.html) used by AngularJS. In this system every issue is assigned frequency and severity based on which the total user pain score is calculated.