beenull/moby
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Update triage process with more labels

Browse source 
Describe new labels in the triage process
to improve the triage workflow / efficiency

Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
This commit is contained in:
Sebastiaan van Stijn 2016-09-27 17:03:44 +02:00
parent 8863a9f62c
commit 0cd4d7de43
No known key found for this signature in database
GPG key ID: 76698F39D527CE8C
1 changed files with 13 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
project/ISSUE-TRIAGE.md
View file

@ -78,7 +78,7 @@ have:
| area/testing | | area/testing |
| area/volumes | | area/volumes |
### Platform #### Platform
| Platform | | Platform |
|---------------------------| |---------------------------|
@ -105,6 +105,18 @@ written a whole plugin for Docker in a personal project and never contributed to
Docker. With that kind of experience, you could take on an <strong Docker. With that kind of experience, you could take on an <strong
class="gh-label expert">exp/expert</strong> level task. class="gh-label expert">exp/expert</strong> level task.
#### Triage status
To communicate the triage status with other collaborators, you can apply status
labels to issues. These labels prevent duplicating effort.
| Status | Description |
|-------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| status/confirmed | You triaged the issue, and were able to reproduce the issue. Always leave a comment how you reproduced, so that the person working on resolving the issue has a way to set up a test-case.
| status/accepted | Apply to enhancements / feature requests that we think are good to have. Adding this label helps contributors find things to work on.
| status/more-info-needed | Apply this to issues that are missing information (e.g. no `docker version` or `docker info` output, or no steps to reproduce), or require feedback from the reporter. If the issue is not updated after a week, it can generally be closed.
| status/needs-attention | Apply this label if an issue (or PR) needs more eyes.
### 3. Prioritizing issue ### 3. Prioritizing issue
When, and only when, an issue is attached to a specific milestone, the issue can be labeled with the When, and only when, an issue is attached to a specific milestone, the issue can be labeled with the