diff options
| author | Sebastiaan van Stijn <github@gone.nl> | 2016-09-27 17:03:44 +0200 |
|---|---|---|
| committer | Sebastiaan van Stijn <github@gone.nl> | 2016-10-17 10:01:53 -0700 |
| commit | 0cd4d7de43d785af74d13029c736c6feec4e23d4 (patch) | |
| tree | 942ff7a41179262b94cce03791cced19f71d832a /project | |
| parent | 8863a9f62cb16fbdbb318165ffc8140aeb32c597 (diff) | |
| download | docker-0cd4d7de43d785af74d13029c736c6feec4e23d4.tar.gz | |
Update triage process with more labels
Describe new labels in the triage process
to improve the triage workflow / efficiency
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Diffstat (limited to 'project')
| -rw-r--r-- | project/ISSUE-TRIAGE.md | 14 |
1 files changed, 13 insertions, 1 deletions
diff --git a/project/ISSUE-TRIAGE.md b/project/ISSUE-TRIAGE.md index 35bacdb314..95cb2f1b95 100644 --- a/project/ISSUE-TRIAGE.md +++ b/project/ISSUE-TRIAGE.md @@ -78,7 +78,7 @@ have: | area/testing | | area/volumes | -### 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 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 When, and only when, an issue is attached to a specific milestone, the issue can be labeled with the |