diff options
| author | Eric Johnson <ejohnson@erics-imac.lan> | 2017-12-30 06:21:12 +0300 |
|---|---|---|
| committer | Eric Johnson <ejohnson@erics-imac.lan> | 2017-12-30 06:21:12 +0300 |
| commit | 16475cab2dcf335d4f4ea1ca1bc30710adc38a2a (patch) | |
| tree | 20aa6fe3147644d8705113200b94e46aae13fc63 | |
| parent | ff077cf7dc5cfd7c6c6206d801ea3f326f7af1aa (diff) | |
Draft Priority label set
| -rw-r--r-- | CONTRIBUTING.md | 17 |
1 files changed, 9 insertions, 8 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 01d4a546b97..14bb0381d4a 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -178,16 +178,17 @@ indicate if an issue needs backend work, frontend work, or both. Team labels are always capitalized so that they show up as the first label for any issue. -### Priority labels (~Deliverable and ~Stretch) +### Priority labels (~P1, ~P2, etc.) Priority labels help us clearly communicate expectations of the work for the -release. There are two levels of priority labels: - -- ~Deliverable: Issues that are expected to be delivered in the current - milestone. -- ~Stretch: Issues that are a stretch goal for delivering in the current - milestone. If these issues are not done in the current release, they will - strongly be considered for the next release. +release. + +| Label | Meaning | Product _e.g._ | Security _e.g._ | +|-------|-----------------------------------|----------------------|-----------------------------------------------| +| ~P1 | Handle immediately | Critical feature | SQL Injection, Authentication Bypass | +| ~P2 | Handle in the current release | Important feature | Cross-site Scripting, Resource exhaustion DoS | +| ~P3 | Schedule for a subsequent release | Nice-to-have feature | Tab nabbing, Path disclosure | +| ~P4 | Trivial, may not do | Suggestion | New feature, Remove dangerous protocol | ### Label for community contributors (~"Accepting Merge Requests") |