masscollaborationlabs/emacs
2
0
Fork 0
mirror of https://github.com/masscollaborationlabs/emacs.git synced 2025-07-06 12:19:37 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Some precisions to bug handling

Browse source 
* admin/admin.el (reminder-for-release-blocking-bugs): Add date to subject.

* admin/notes/bug-triage:
* admin/notes/bugtracker: Minor precisions.
This commit is contained in:
Michael Albinus 2020-08-30 15:43:58 +02:00
parent dddc971f0e
commit 29708cbde7
3 changed files with 15 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

3
admin/admin.el
View file

@ -951,7 +951,8 @@ changes (in a non-trivial way). This function does not check for that."
(lambda () ; posthook (lambda () ; posthook
(goto-char (point-min)) (goto-char (point-min))
(mail-position-on-field "subject") (mail-position-on-field "subject")
(insert (format "Release-blocking bugs for Emacs %s" version)) (insert (format "Reminder: release-blocking bugs for Emacs %s (%s)"
version (format-time-string "%F" nil "UTC0")))
(mail-text) (mail-text)
(delete-region (point) (point-max)) (delete-region (point) (point-max))
(insert " (insert "

10
admin/notes/bug-triage
View file

@ -11,7 +11,11 @@ interface via org-mode.
The goal of this triage is to prune down the list of old bugs, closing The goal of this triage is to prune down the list of old bugs, closing
the ones that are not reproducible on the current release. the ones that are not reproducible on the current release.
1. To start, enter debbugs mode (either debbugs-gnu, debbugs-org, or via the 0. To start, check the most relevant bugs blocking a release by
calling debbugs-gnu-emacs-release-blocking-reports. If you want
to check this for another Emacs version but the next-to-be-released-one,
use the "C-u" prefix.
1. After that, enter debbugs mode (either debbugs-gnu, debbugs-org, or via the
web browser), and accept the default list option of bugs that have severity web browser), and accept the default list option of bugs that have severity
serious, important, or normal. serious, important, or normal.
2. For each bug, we want to primarily make sure it is still 2. For each bug, we want to primarily make sure it is still
@ -20,7 +24,7 @@ the ones that are not reproducible on the current release.
suggested checklist to follow for handling these bugs, along with suggested checklist to follow for handling these bugs, along with
example replies. Closing, tagging, etc., are done example replies. Closing, tagging, etc., are done
with debbugs control messages, which in debbugs-gnu is initiated with debbugs control messages, which in debbugs-gnu is initiated
with a "C". with a "C" or "E".
[ ] Read the mail thread for the bug. Find out if anyone has [ ] Read the mail thread for the bug. Find out if anyone has
been able to reproduce this on the current release. If been able to reproduce this on the current release. If
someone has been able to, then your work is finished for this someone has been able to, then your work is finished for this
@ -87,7 +91,7 @@ necessary information for others to act on.
For each new bug, ask the following questions: For each new bug, ask the following questions:
1. Is the bug report written in a way to be easy to reproduce (starts from 1. Is the bug report written in a way to be easy to reproduce (starts from
emacs -Q, etc.)? If not, ask the reporter to try and reproduce it on an "emacs -Q", etc.)? If not, ask the reporter to try and reproduce it on an
emacs without customization. emacs without customization.
2. Is the bug report written against the latest emacs? If not, try to 2. Is the bug report written against the latest emacs? If not, try to
reproduce on the latest version, and if it can't be reproduced, ask the reproduce on the latest version, and if it can't be reproduced, ask the

13
admin/notes/bugtracker
View file

@ -33,7 +33,7 @@ By mailing commands to control@debbugs.gnu.org. Place commands at the
start of the message body, one per line. start of the message body, one per line.
severity 123 serious|important|normal|minor|wishlist severity 123 serious|important|normal|minor|wishlist
tags 123 moreinfo|unreproducible|wontfix|patch tags 123 moreinfo|unreproducible|wontfix|patch|notabug
* More detailed information * More detailed information
@ -185,7 +185,7 @@ Basically, reply only to the numbered bug address (and any individual
people's addresses). Do not send mail direct to bug-gnu-emacs or people's addresses). Do not send mail direct to bug-gnu-emacs or
emacs-pretest-bug unless you are reporting a new bug. emacs-pretest-bug unless you are reporting a new bug.
** To close bug #123 (for example), send mail ** To close bug#123 (for example), send mail
To: 123-done@debbugs.gnu.org To: 123-done@debbugs.gnu.org
@ -260,7 +260,7 @@ reopen 123
*** Bugs can be tagged in various ways (eg wontfix, patch, etc). *** Bugs can be tagged in various ways (eg wontfix, patch, etc).
The available tags are: The available tags are:
patch wontfix moreinfo unreproducible fixed notabug security confirmed patch wontfix moreinfo unreproducible fixed notabug help security confirmed easy
See https://debbugs.gnu.org/Developer#tags See https://debbugs.gnu.org/Developer#tags
The list of tags can be prefixed with +, - or =, meaning to add (the The list of tags can be prefixed with +, - or =, meaning to add (the
default), remove, or reset the tags. E.g.: default), remove, or reset the tags. E.g.:
@ -290,10 +290,9 @@ limited, predefined set of normal tags are available (see above).
2) A usertag is associated with a specific user. This is normally 2) A usertag is associated with a specific user. This is normally
an email address (with an "@" sign and least 4 characters after the "@"), an email address (with an "@" sign and least 4 characters after the "@"),
but on debbugs.gnu.org, the definition is less strict - anything with but on debbugs.gnu.org, it can also be a package name. For personal tags,
5 or more alphanumeric characters will work. For personal tags,
using an email address is still recommended. Please only use the using an email address is still recommended. Please only use the
"emacs" user, or other short users, for "official" tags. "emacs" user for "official" tags.
You set usertags in the same way as tags, by talking to the control server. You set usertags in the same way as tags, by talking to the control server.
One difference is that you can also specify the associated user. One difference is that you can also specify the associated user.
@ -307,7 +306,7 @@ a) In a control message:
user emacs # or email@example.com user emacs # or email@example.com
usertags 1234 any-tag-you-like usertags 1234 any-tag-you-like
This will add a usertag "any-tag-you-like" to bug 1234. The tag will This will add a usertag "any-tag-you-like" to bug#1234. The tag will
be associated with the user "emacs". If you omit the first line, be associated with the user "emacs". If you omit the first line,
the tag will be associated with your email address. the tag will be associated with your email address.