From a93ae6d86dfece8525a2d4ef7f9d4f269a208a78 Mon Sep 17 00:00:00 2001 From: Virgil Dupras Date: Sun, 19 Apr 2015 19:25:21 -0400 Subject: [PATCH] Updated issue labels (markdown) --- issue-labels.md | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/issue-labels.md b/issue-labels.md index 2ec41d2..e2c6978 100644 --- a/issue-labels.md +++ b/issue-labels.md @@ -10,9 +10,5 @@ Issue types Workflow status --- -* **new:** This issue is new and hasn't been reviewed yet. For a bug, it means that it hasn't been reproduced, and for a feature request, it means it hasn't been accepted. There is no label for this status, but when a ticket doesn't have another status label, it is considered new. -* **accepted:** This ticket has been reviewed and accepted by the maintainer. It means that either the bug was reproduced or the feature was accepted for inclusion. -* **thinking:** This issue (most of the time, a feature) is still under discussion, either on whether it should be implemented, or on how to do it. For a bug, it might mean that it still needs reproducing, but, unlike the "hold" status, we don't say that it can't be reproduced. +* **mentored:** This ticket is seen as a good introductory task (that is, it should be relatively easy to complete). If you're interested getting involved in the project, it's likely a good place to start. If you need guidance, don't hesitate call for mentors at #300. * **hold:** Some external feedback is needed to either continue working on the issue, or to close it. Most of the time, it's a bug that can't be reproduced. It needs more details from people who experience the bug so it can be reproduced. - -There used to be status for closed ticket (invalid and duplicate), but they didn't serve much purpose and were removed. Comments in the tickets indicate how they were processed. \ No newline at end of file