| 1 |
On Mon, 6 Sep 2010 10:39:59 +0200 |
| 2 |
Dirkjan Ochtman <djc@g.o> wrote: |
| 3 |
|
| 4 |
> On Mon, Sep 6, 2010 at 10:32, Robin H. Johnson <robbat2@g.o> wrote: |
| 5 |
> > After a discussion on IRC, a few of us were considering the value of |
| 6 |
> > adding suggestions on handling of bugs in Bugzilla from a developer (and |
| 7 |
> > editbugs user) perspective. |
| 8 |
> |
| 9 |
> Good idea, I've been confused about the interaction models here. |
| 10 |
> |
| 11 |
> > 1. General case |
| 12 |
> > - You should only close bugs that you are assigned or if you (or an alias |
| 13 |
> > you represent) just fixed them. |
| 14 |
|
| 15 |
Prefix "Once assigned,". |
| 16 |
|
| 17 |
Can we add a point about bug-wranglers not messing with bugs after they've |
| 18 |
been assigned? I've had someone closing bugs filed directly from a dev to my |
| 19 |
herd because they didn't include emerge --info. |
| 20 |
|
| 21 |
> > - If you fix a bug and AREN'T already getting mail for it, you should |
| 22 |
> > add yourself to the CC list, to listen for regressions or responses |
| 23 |
> > to TESTREQUEST. |
| 24 |
> |
| 25 |
> Only add arches to stabilization requests if you're a maintainer? |
| 26 |
|
| 27 |
No. If the maintainer doesn't respond in a reasonable amount of time then |
| 28 |
I'm adding arches myself. If this weren't allowed then the GCC stabilization |
| 29 |
bugs would take approx 8 years to fix. |
| 30 |
|
| 31 |
|
| 32 |
-- |
| 33 |
fonts, gcc-porting, we hold our breath, we spin around the world |
| 34 |
toolchain, wxwidgets you and me cling to the outside of the earth |
| 35 |
@ gentoo.org EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662 |
Archives