Re: RFC Bugzilla interaction guide for devs & editbugs users
Dirkjan Ochtman <djc <at> gentoo.org>
2010-09-06 08:39:59 GMT
On Mon, Sep 6, 2010 at 10:32, Robin H. Johnson <robbat2 <at> gentoo.org> wrote:
> After a discussion on IRC, a few of us were considering the value of
> adding suggestions on handling of bugs in Bugzilla from a developer (and
> editbugs user) perspective.
Good idea, I've been confused about the interaction models here.
> 1. General case
> - You should only close bugs that you are assigned or if you (or an alias
> you represent) just fixed them.
> - If you fix a bug and AREN'T already getting mail for it, you should
> add yourself to the CC list, to listen for regressions or responses
> to TESTREQUEST.
Only add arches to stabilization requests if you're a maintainer?
> 2. Special cases
> 2.1. STABLEREQ, KEYWORDREQ
> The last arch on the list should close the bug when they have completed
> the action.
> 2.2. Security bugs
> The developer should comment, but ONLY members of the security team
> - change whiteboard
> - add/remove arches
> - change bug status/reso
The arches can still remove themselves when they've done whatever they
needed to do, right?