comparison admin/notes/bugtracker @ 107943:0ddcd935235c

* admin/notes/bugtracker: Minor updates.
author Glenn Morris <rgm@gnu.org>
date Tue, 13 Apr 2010 19:36:48 -0700
parents 883859fd8369
children 85d6810f63ed 6926686a73a0
comparison
equal deleted inserted replaced
107942:3022f1f90ee2 107943:0ddcd935235c
2 2
3 The Emacs Bug Tracker can be found at http://debbugs.gnu.org/ 3 The Emacs Bug Tracker can be found at http://debbugs.gnu.org/
4 4
5 * Quick-start guide 5 * Quick-start guide
6 6
7 This is 95% of all you will ever need. 7 This is 95% of all you will ever need to know.
8 8
9 ** How do I report a bug? 9 ** How do I report a bug?
10 Use M-x report-emacs-bug, or send mail to bug-gnu-emacs@gnu.org. 10 Use M-x report-emacs-bug, or send mail to bug-gnu-emacs@gnu.org.
11 If you want to Cc someone, use an "X-Debbugs-CC" header instead. 11 If you want to Cc someone, use an "X-Debbugs-CC" header instead.
12 12
32 32
33 * More detailed information 33 * More detailed information
34 34
35 For a list of all bugs, see http://debbugs.gnu.org/db/pa/lemacs.html 35 For a list of all bugs, see http://debbugs.gnu.org/db/pa/lemacs.html
36 This is a static page, updated once a day. There is also a dynamic 36 This is a static page, updated once a day. There is also a dynamic
37 list, generated on request, but since there are many bug reports this 37 list, generated on request. This accepts various options, eg to see
38 is slow and not recommended. 38 the most recent bugs:
39
40 http://debbugs.gnu.org/cgi/pkgreport.cgi?newest=100
41
42 Or follow the links on the front page http://debbugs.gnu.org .
39 43
40 ** How do I report a bug in Emacs now? 44 ** How do I report a bug in Emacs now?
41 The same way as you always did. Send mail to bug-gnu-emacs@gnu.org, 45 The same way as you always did. Send mail to bug-gnu-emacs@gnu.org,
42 or use M-x report-emacs-bug. 46 or use M-x report-emacs-bug.
43 47
89 (e.g. bug-cc-mode@gnu.org), do NOT just use a Cc: header. 93 (e.g. bug-cc-mode@gnu.org), do NOT just use a Cc: header.
90 Instead, use "X-Debbugs-CC:". This ensures the Cc address will get a 94 Instead, use "X-Debbugs-CC:". This ensures the Cc address will get a
91 mail with the bug report number in. If you do not do this, each reply 95 mail with the bug report number in. If you do not do this, each reply
92 in the subsequent discussion will end up creating a new bug. 96 in the subsequent discussion will end up creating a new bug.
93 This is annoying. 97 This is annoying.
98
99 (So annoying that a form of message-id tracking has been implemented
100 to hopefully stop this happening, but it is still better to use X-Debbugs-CC.)
94 101
95 If a new report contains X-Debbugs-CC in the input, this is 102 If a new report contains X-Debbugs-CC in the input, this is
96 converted to a real Cc header in the output. (See Bug#1720). 103 converted to a real Cc header in the output. (See Bug#1720).
97 It is also merged into the Resent-CC header (see below). 104 It is also merged into the Resent-CC header (see below).
98 105
189 196
190 Package: emacs 197 Package: emacs
191 Version: 23.0.60 198 Version: 23.0.60
192 Severity: minor 199 Severity: minor
193 200
194 Optionally, add a sub-package, eg Package: emacs,calendar. 201 This can also include tags. Some things (e.g. submitter) don't seem to
195 This can include tags. Some things (e.g. submitter) don't seem to
196 work here. 202 work here.
197 203
198 Otherwise, send mail to the control server, control@debbugs.gnu.org. 204 Otherwise, send mail to the control server, control@debbugs.gnu.org.
199 At the start of the message body, supply the desired commands, one per 205 At the start of the message body, supply the desired commands, one per
200 line: 206 line:
227 233
228 http://debbugs.gnu.org/... 234 http://debbugs.gnu.org/...
229 235
230 123 # given bug number 236 123 # given bug number
231 123;mbox=yes # mbox version of given bug 237 123;mbox=yes # mbox version of given bug
232 package # bugs in given package (don't use "emacs" - too many bugs!) 238 package # bugs in given package
233 from:submitter@email.address 239 from:submitter@email.address
234 severity:severity # all bugs of given severity 240 severity:severity # all bugs of given severity
235 tag:tag # all bugs with given tag 241 tag:tag # all bugs with given tag
236 242
237 ** Usertags 243 ** Usertags
279 The search interface is not as advanced as for normal tags. You need 285 The search interface is not as advanced as for normal tags. You need
280 to construct the relevant url yourself rather than just typing in a 286 to construct the relevant url yourself rather than just typing in a
281 search box. The only piece you really need to add is the "users" 287 search box. The only piece you really need to add is the "users"
282 portion, the rest has the same syntax as normal. 288 portion, the rest has the same syntax as normal.
283 289
290 **** To browse bugs by usertag:
291 http://debbugs.gnu.org/cgi/pkgindex.cgi?indexon=users
292
284 **** To find all bugs usertagged by a given email address: 293 **** To find all bugs usertagged by a given email address:
285 294
286 http://debbugs.gnu.org/cgi/pkgreport.cgi?users=bug-gnu-emacs@gnu.org 295 http://debbugs.gnu.org/cgi/pkgreport.cgi?users=bug-gnu-emacs@gnu.org
287 296
288 (Supposedly, the "users" field can be a comma-separated list of more 297 (Supposedly, the "users" field can be a comma-separated list of more
357 366
358 *** To remove a "fixed" mark: 367 *** To remove a "fixed" mark:
359 notfixed 123 23.0.60 368 notfixed 123 23.0.60
360 369
361 *** To assign or reassign a bug to a package or list of packages: 370 *** To assign or reassign a bug to a package or list of packages:
362 reassign 1234 emacs,cc-mode 371 reassign 1234 emacs
363 372
364 ** To remove spam from the tracker, move it to the `spam' pseudo-package: 373 ** To remove spam from the tracker, move it to the `spam' pseudo-package:
365 reassign 123 spam 374 reassign 123 spam
366 375
367 ** To change the title of a bug: 376 ** To change the title of a bug: