procyberian/emacs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

* admin/notes/bug-triage: Fix bug priorities. Explain colors in debbugs-gnu.

Browse source
This commit is contained in:
Michael Albinus 2016-02-09 20:04:34 +01:00
parent a6d6753938
commit 2b045dc036
1 changed files with 9 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
admin/notes/bug-triage
View file

@ -72,7 +72,7 @@ the ones that are not reproducible on the current release.
weeks, I'll just close this bug as unreproducible."
[ ] Check that the priority is reasonable. Most bugs should be
marked as normal, but crashers and security issues can be
marked as "severe".
marked as serious.
4. Your changes will take some time to take effect. After a period of minutes
to hours, you will get a mail telling you the control message has been
processed. At this point, if there were no errors detected, you and
@ -95,8 +95,14 @@ For each new bug, ask the following questions:
reproduce on the latest version, and if it can't be reproduced, ask the
reporter to try again with the latest version.
3. Is the bug the same as another bug? If so, merge the bugs.
4. What is the priority of the bug? Add a priority: critical, grave, serious,
important, normal, minor, or wishlist.
4. What is the priority of the bug? Add a priority: serious, important,
normal, minor, or wishlist.
5. Who should be the owner? This depends on what component the bug is part
of. You can look at the admin/MAINTAINERS file (then you can just search
emacs-devel to match the name with an email address).
In the debbugs-gnu buffer, bugs are marked in the "State" column
according to the communication flow. Red bugs mean that nobody has
answered, these bugs need primary attention. Green bugs flag that
there is a recent communication about, and orange bugs flag that the
bug hasn't been touched for at least two weeks.