1 |
On Mon, Sep 6, 2010 at 10:32, Robin H. Johnson <robbat2@g.o> wrote: |
2 |
> After a discussion on IRC, a few of us were considering the value of |
3 |
> adding suggestions on handling of bugs in Bugzilla from a developer (and |
4 |
> editbugs user) perspective. |
5 |
|
6 |
Good idea, I've been confused about the interaction models here. |
7 |
|
8 |
> 1. General case |
9 |
> - You should only close bugs that you are assigned or if you (or an alias |
10 |
> you represent) just fixed them. |
11 |
> - If you fix a bug and AREN'T already getting mail for it, you should |
12 |
> add yourself to the CC list, to listen for regressions or responses |
13 |
> to TESTREQUEST. |
14 |
|
15 |
Only add arches to stabilization requests if you're a maintainer? |
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 |
The arches can still remove themselves when they've done whatever they |
30 |
needed to do, right? |
31 |
|
32 |
Cheers, |
33 |
|
34 |
Dirkjan |