Mercurial > emacs
annotate admin/notes/bugtracker @ 101512:80672b7f9b76
Add some addresses for rmail users to ignore.
author | Glenn Morris <rgm@gnu.org> |
---|---|
date | Mon, 26 Jan 2009 02:58:27 +0000 |
parents | 9dea7f9ad305 |
children | fb07b238e55a |
rev | line source |
---|---|
95505 | 1 NOTES ON THE EMACS BUG TRACKER -*- outline -*- |
95445 | 2 |
95505 | 3 The Emacs Bug Tracker can be found at http://emacsbugs.donarmstrong.com/ |
95445 | 4 |
96482 | 5 For a list of all bugs, see http://emacsbugs.donarmstrong.com/emacs |
95445 | 6 |
97973 | 7 ** How do I report a bug in Emacs now? |
8 The same way as you always did. Send mail to bug-gnu-emacs@gnu.org, | |
9 or use M-x report-emacs-bug. | |
10 | |
11 The only differences are: | |
12 | |
13 i) Your report will be assigned a number and generate an automatic reply. | |
14 | |
15 ii) Optionally, you can set some database parameters when you first | |
16 report a bug (see "Setting bug parameters" below). | |
17 | |
98568 | 18 iii) If you want to CC: someone, use X-Debbugs-CC: (this is important; |
19 see below). | |
97973 | 20 |
21 Once your report is filed and assigned a number, it is sent out to the | |
22 bug mailing list. In some cases, it may be appropriate to just file a | |
23 bug, without sending out a copy. To do this, send mail to | |
24 quiet@emacsbugs.donarmstrong.com. | |
25 | |
26 ** How do I reply to an existing bug report? | |
27 Reply to 123@emacsbugs.donarmstrong.com, replacing 123 with the number | |
98513 | 28 of the bug you are interested in. NB this only sends mail to the |
29 bug-list, it does NOT (?) send a CC to the original bug submitter. | |
30 So you need to explicitly CC him/her (and anyone else you like). | |
31 | |
32 (Many people think the submitter SHOULD be automatically subscribed | |
33 to subsequent discussion, but this does not seem to be implemented. | |
34 See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=37078) | |
35 | |
36 Do NOT send a separate copy to the bug list, since this may generate a | |
37 new report. The only time to send mail to the bug list is to create a | |
38 new report. | |
95445 | 39 |
101299
e087ec9d57c0
Add yet more addresses to avoid in replies.
Glenn Morris <rgm@gnu.org>
parents:
101164
diff
changeset
|
40 Gnus users can add "\\(\\(emacs-pretest-bug\\|bug-gnu-emacs\\)@gnu\\.org\\|\ |
e087ec9d57c0
Add yet more addresses to avoid in replies.
Glenn Morris <rgm@gnu.org>
parents:
101164
diff
changeset
|
41 \\(submit\\|control\\)@emacsbugs\\.donarmstrong\\.com\\)" |
101512
80672b7f9b76
Add some addresses for rmail users to ignore.
Glenn Morris <rgm@gnu.org>
parents:
101312
diff
changeset
|
42 to message-dont-reply-to-names. |
80672b7f9b76
Add some addresses for rmail users to ignore.
Glenn Morris <rgm@gnu.org>
parents:
101312
diff
changeset
|
43 |
80672b7f9b76
Add some addresses for rmail users to ignore.
Glenn Morris <rgm@gnu.org>
parents:
101312
diff
changeset
|
44 Similarly, RMAIL users can use rmail-dont-reply-to-names. They might |
80672b7f9b76
Add some addresses for rmail users to ignore.
Glenn Morris <rgm@gnu.org>
parents:
101312
diff
changeset
|
45 also need to ignore "bug-submit-list@donarmstrong.com" since it |
80672b7f9b76
Add some addresses for rmail users to ignore.
Glenn Morris <rgm@gnu.org>
parents:
101312
diff
changeset
|
46 appears in the "Resent-To" header of reports, and for a long time |
80672b7f9b76
Add some addresses for rmail users to ignore.
Glenn Morris <rgm@gnu.org>
parents:
101312
diff
changeset
|
47 RMAIL erroneously included this address in replies. Likewise for |
80672b7f9b76
Add some addresses for rmail users to ignore.
Glenn Morris <rgm@gnu.org>
parents:
101312
diff
changeset
|
48 "owner@emacsbugs.donarmstrong.com", which can appear in the |
80672b7f9b76
Add some addresses for rmail users to ignore.
Glenn Morris <rgm@gnu.org>
parents:
101312
diff
changeset
|
49 "Resent-CC:" header (but it is possible, outside of normal bug |
80672b7f9b76
Add some addresses for rmail users to ignore.
Glenn Morris <rgm@gnu.org>
parents:
101312
diff
changeset
|
50 reporting, that you might want to have a dialog with this address). |
100191 | 51 |
96482 | 52 ** When reporting a bug, to send a Cc to another address |
98568 | 53 (e.g. bug-cc-mode@gnu.org), do NOT just use a Cc: header. |
96482 | 54 Instead, use "X-Debbugs-CC:". This ensures the Cc address will get a |
98568 | 55 mail with the bug report number in. If you do not do this, each reply |
56 in the subsequent discussion will end up creating a new bug. This is | |
57 annoying. | |
95486 | 58 |
95505 | 59 ** To not get acknowledgement mail from the tracker, |
98513 | 60 add an "X-Debbugs-No-Ack:" header (with any value). If you use Gnus, |
61 you can add an element to gnus-posting-styles to do this automatically, eg: | |
62 | |
63 ("gnu-emacs\\(-pretest\\)?-bug" | |
64 ("X-Debbugs-No-Ack" "yes")) | |
65 | |
66 (adjust the regexp according to the name you use for the bug lists) | |
95486 | 67 |
96467 | 68 ** To record a bug in the tracker without sending mail to the bug list. |
69 This can be useful to make a note of something discussed on | |
96468 | 70 emacs-devel that needs fixing. In other words, this can be the |
71 equivalent of adding something to FOR-RELEASE. | |
96467 | 72 |
73 To: quiet@emacsbugs.donarmstrong.com | |
74 [headers end] | |
75 Package: emacs | |
76 Version: 23.0.60 | |
77 Severity: minor | |
78 | |
79 Remember to fix FOO, as discussed on emacs-devel at http://... . | |
80 | |
96401 | 81 ** Not interested in tracker control messages (tags being set, etc)? |
82 Discard mails matching: | |
83 | |
84 ^X-Emacs-PR-Message: transcript | |
85 | |
96402 | 86 When you close a bug, you get a message matching: |
87 | |
88 ^X-Emacs-PR-Message: closed | |
89 | |
96401 | 90 ** How to avoid multiple copies of mails. |
91 When you reply to a bug, respect the Reply-To address, ie send mail | |
92 only to the submitter address and the numbered bug address. Do not | |
93 send mail direct to bug-gnu-emacs or emacs-pretest-bug unless you are | |
94 reporting a new bug. | |
95 | |
95505 | 96 ** To close bug #123 (for example), send mail |
95486 | 97 |
96482 | 98 To: 123-done@emacsbugs.donarmstrong.com |
95445 | 99 |
100 with a brief explanation in the body as to why the bug was closed. | |
101 | |
96482 | 102 ** Setting bug parameters. |
103 There are two ways to set the parameters of bugs in the database | |
104 (tags, severity level, etc). When you report a new bug, you can | |
105 provide a "pseudo-header" at the start of the report, eg: | |
95445 | 106 |
96482 | 107 Package: emacs |
108 Version: 23.0.60 | |
109 Severity: minor | |
95505 | 110 |
97973 | 111 Optionally, add a sub-package, eg Package: emacs,calendar. |
97782 | 112 This can include tags. Some things (e.g. submitter) don't seem to |
113 work here. | |
114 | |
96482 | 115 Otherwise, send mail to the control server, control@emacsbugs.donarmstrong.com. |
116 At the start of the message body, supply the desired commands, one per | |
117 line: | |
95505 | 118 |
96482 | 119 command bug-number [arguments] |
120 ... | |
121 quit|stop|thank|thanks|thankyou|thank you | |
95473 | 122 |
96482 | 123 The control server ignores anything after the last line above. So you |
124 can place control commands at the beginning of a reply to a bug | |
96506 | 125 report, and Bcc: the control server (note the commands have no effect |
126 if you just send them to the bug-report number). Bcc: is better than Cc: | |
127 in case people use Reply-to-All in response. | |
95473 | 128 |
96482 | 129 Some useful control commands: |
130 | |
131 *** To reopen a closed bug: | |
132 reopen 123 | |
133 | |
134 *** Bugs can be tagged in various ways (eg wontfix, patch, etc). | |
96506 | 135 The available tags are: |
136 patch wontfix moreinfo unreproducible fixed notabug | |
137 Note that the list at http://emacsbugs.donarmstrong.com/Developer#tags | |
138 is incorrect, at least for Emacs. | |
139 The list of tags can be prefixed with +, - or =, meaning to add (the | |
140 default), remove, or reset the tags. E.g.: | |
95445 | 141 |
96506 | 142 tags 123 + wontfix |
95505 | 143 |
96482 | 144 *** To merge bugs: |
145 Eg when bad replies create a bunch of new bugs for the same report. | |
97989 | 146 Bugs must all be in the same state (e.g. same package(s) and severity), |
147 but need not have the same tags (tags are merged). E.g.: | |
95505 | 148 |
96482 | 149 merge 123 124 125 ... |
96389 | 150 |
97989 | 151 Note that merging does not affect titles. In particular, a "retitle" |
152 of merged bugs only affects individual bugs, not all of them. | |
153 | |
96482 | 154 *** Forcing a merge: |
97989 | 155 Like `merge', but bugs need not be in the same state. The packages |
156 must still match though. The first one listed is the master. E.g.: | |
96469 | 157 |
96482 | 158 forcemerge 123 124 125 ... |
96469 | 159 |
100191 | 160 Note: you cannot merge with an archived bug - you must unarchive it first. |
161 | |
97713 | 162 *** To unmerge bugs: |
163 To disconnect a bug from all bugs it is merged with: | |
164 | |
165 unmerge 123 | |
166 | |
167 This command accepts only one bug number. | |
168 | |
98523 | 169 *** To clone bugs: |
170 Useful when one report refers to more than one bug. | |
171 | |
172 clone 123 -1 [-2 ...] | |
173 retitle -1 second bug | |
174 retitle -2 third bug | |
175 | |
176 The negative numbers provide a way to refer to the cloned bugs (which | |
177 will be assigned proper numbers). | |
178 | |
96482 | 179 *** To set severity: |
180 severity 123 critical|grave|serious|important|normal|minor|wishlist | |
96389 | 181 |
182 See http://emacsbugs.donarmstrong.com/Developer#severities for the meanings. | |
96447 | 183 |
97931 | 184 *** To set the owner of a bug: |
96482 | 185 owner 123 A Hacker <none@example.com> |
96447 | 186 |
187 The shorthand `!' means your own address. | |
188 | |
97931 | 189 *** To remove the owner of a bug: |
190 noowner 123 | |
191 | |
96482 | 192 *** To mark a bug as fixed in a particular version: |
193 fixed 123 23.0.60 | |
96447 | 194 |
96506 | 195 *** To remove a "fixed" mark: |
196 notfixed 123 23.0.60 | |
197 | |
96482 | 198 ** To remove spam from the tracker, move it to the `spam' pseudo-package: |
199 reassign 123 spam | |
97753 | 200 |
201 ** To change the title of a bug: | |
202 retitle 123 Some New Title | |
203 | |
204 ** To change the submitter address: | |
205 submitter 123 none@example.com | |
97782 | 206 |
207 Note that it does not seem to work to specify "Submitter:" in the | |
208 pseudo-header when first reporting a bug. | |
100967 | 209 |
210 ** How does archiving work? | |
211 You can still send mail to a bug after it is closed. After 28 days with | |
212 no activity, the bug is archived, at which point no more changes can | |
213 be made. If you try to send mail to the bug after that (or merge with | |
214 it), it will be rejected. To make any changes, you must unarchive it first: | |
215 | |
216 unarchive 123 | |
217 | |
218 The bug will be re-archived after the next 28 day period of no activity. | |
101312
9dea7f9ad305
Mention limiting number of bugs displayed on web-page.
Glenn Morris <rgm@gnu.org>
parents:
101299
diff
changeset
|
219 |
9dea7f9ad305
Mention limiting number of bugs displayed on web-page.
Glenn Morris <rgm@gnu.org>
parents:
101299
diff
changeset
|
220 ** The web-page with the list of bugs is slow to load |
9dea7f9ad305
Mention limiting number of bugs displayed on web-page.
Glenn Morris <rgm@gnu.org>
parents:
101299
diff
changeset
|
221 |
9dea7f9ad305
Mention limiting number of bugs displayed on web-page.
Glenn Morris <rgm@gnu.org>
parents:
101299
diff
changeset
|
222 It's a function of the number of displayed bugs. You can speed things |
9dea7f9ad305
Mention limiting number of bugs displayed on web-page.
Glenn Morris <rgm@gnu.org>
parents:
101299
diff
changeset
|
223 up by only looking at the newest 100 bugs: |
9dea7f9ad305
Mention limiting number of bugs displayed on web-page.
Glenn Morris <rgm@gnu.org>
parents:
101299
diff
changeset
|
224 |
9dea7f9ad305
Mention limiting number of bugs displayed on web-page.
Glenn Morris <rgm@gnu.org>
parents:
101299
diff
changeset
|
225 http://emacsbugs.donarmstrong.com/cgi-bin/pkgreport.cgi?newest=100;package=emacs |
9dea7f9ad305
Mention limiting number of bugs displayed on web-page.
Glenn Morris <rgm@gnu.org>
parents:
101299
diff
changeset
|
226 |
9dea7f9ad305
Mention limiting number of bugs displayed on web-page.
Glenn Morris <rgm@gnu.org>
parents:
101299
diff
changeset
|
227 The above page is accessible from the "Options" section at the end of |
9dea7f9ad305
Mention limiting number of bugs displayed on web-page.
Glenn Morris <rgm@gnu.org>
parents:
101299
diff
changeset
|
228 the "main list of bugs" page. Select bugs "in package" = emacs; |
9dea7f9ad305
Mention limiting number of bugs displayed on web-page.
Glenn Morris <rgm@gnu.org>
parents:
101299
diff
changeset
|
229 "newest bugs" = 100. (I have no idea how you get to that Options |
9dea7f9ad305
Mention limiting number of bugs displayed on web-page.
Glenn Morris <rgm@gnu.org>
parents:
101299
diff
changeset
|
230 section without having to go through the bug list page first...) |