1 |
Hi, |
2 |
|
3 |
After a discussion on IRC, a few of us were considering the value of |
4 |
adding suggestions on handling of bugs in Bugzilla from a developer (and |
5 |
editbugs user) perspective. |
6 |
|
7 |
These is the simplest set I have to start, but I'd really like other |
8 |
comments and ideas. |
9 |
|
10 |
1. General case |
11 |
- You should only close bugs that you are assigned or if you (or an alias |
12 |
you represent) just fixed them. |
13 |
- If you fix a bug and AREN'T already getting mail for it, you should |
14 |
add yourself to the CC list, to listen for regressions or responses |
15 |
to TESTREQUEST. |
16 |
|
17 |
2. Special cases |
18 |
2.1. STABLEREQ, KEYWORDREQ |
19 |
The last arch on the list should close the bug when they have completed |
20 |
the action. |
21 |
|
22 |
2.2. Security bugs |
23 |
The developer should comment, but ONLY members of the security team |
24 |
should: |
25 |
- change whiteboard |
26 |
- add/remove arches |
27 |
- change bug status/reso |
28 |
|
29 |
-- |
30 |
Robin Hugh Johnson |
31 |
Gentoo Linux: Developer, Trustee & Infrastructure Lead |
32 |
E-Mail : robbat2@g.o |
33 |
GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85 |