aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorPaul Eggert2016-09-26 17:28:17 -0700
committerPaul Eggert2016-09-26 17:28:54 -0700
commitf1451d4206ba27fb5ceaeb335f606cd26381bfd7 (patch)
treefc03285a2fc1d6820713d45233278bee222e7a6b
parent3db6defcf43561deb2733446571ca1fc9f589f8f (diff)
downloademacs-f1451d4206ba27fb5ceaeb335f606cd26381bfd7.tar.gz
emacs-f1451d4206ba27fb5ceaeb335f606cd26381bfd7.zip
Stick with debbugs-supported tags in triage
* admin/notes/bug-triage: Stick to the tag "unreproducible", which debbugs supports, rather than suggesting "doneunreproducible" or "unreproducable".
-rw-r--r--admin/notes/bug-triage16
1 files changed, 8 insertions, 8 deletions
diff --git a/admin/notes/bug-triage b/admin/notes/bug-triage
index 4a2a5f392e5..47ce4e071d4 100644
--- a/admin/notes/bug-triage
+++ b/admin/notes/bug-triage
@@ -30,12 +30,12 @@ the ones that are not reproducible on the current release.
30 [ ] Make sure there's enough information to reproduce the bug. 30 [ ] Make sure there's enough information to reproduce the bug.
31 It should be very clear how to reproduce. If not, please ask 31 It should be very clear how to reproduce. If not, please ask
32 for specific steps to reproduce. If you don't get them, and 32 for specific steps to reproduce. If you don't get them, and
33 you can't reproduce without them, you can close as 33 you can't reproduce without them, you can tag the bug report
34 "doneunreproducible". Sometimes there is specific hardware 34 as "unreproducible" and close the bug report. Sometimes this
35 involved, such as particular models of keyboards, or it may 35 involves specific hardware such as particular models of
36 simply involve a platform you don't have access to. It's 36 keyboards, or it may simply involve a platform you don't have
37 fine to ignore those, and let a future triager that is better 37 access to. It's fine to ignore those, and let a future
38 equipped to reproduce it handle it. 38 triager that is better equipped to reproduce it handle it.
39 39
40 An example reply asking for clear reproduction steps would be 40 An example reply asking for clear reproduction steps would be
41 something like: "Hi! In the interest of seeing whether this 41 something like: "Hi! In the interest of seeing whether this
@@ -61,9 +61,9 @@ the ones that are not reproducible on the current release.
61 61
62 If you can't reproduce, state that you can't reproduce it on 62 If you can't reproduce, state that you can't reproduce it on
63 the current release, ask if they can try again against the 63 the current release, ask if they can try again against the
64 current release. Tag the bug as "unreproducable". Wait a 64 current release. Tag the bug as "unreproducible". Wait a
65 few weeks for their reply - if they can reproduce it, then 65 few weeks for their reply - if they can reproduce it, then
66 that's great, otherwise close as "doneunreproducible". 66 that's great, otherwise close the bug report.
67 67
68 Example reply: "I've attempted to reproduce this on the 68 Example reply: "I've attempted to reproduce this on the
69 latest version of emacs, Emacs 25, but haven't been able to. 69 latest version of emacs, Emacs 25, but haven't been able to.