| 1 |
Thanks for the advice, Donnie. I'll try to keep it in mind in my future |
| 2 |
dealings with Bugzilla (you can't get rid of me that easily muhahaha!) |
| 3 |
|
| 4 |
On Sat, 2004-04-03 at 14:28, Seemant Kulleen wrote: |
| 5 |
> On Fri, 2004-04-02 at 18:40, Donnie Berkholz wrote: |
| 6 |
> |
| 7 |
> > Here's a few suggestions, based on personal experience: |
| 8 |
> > |
| 9 |
> > 3) Priority is a very subjective issue. Sure, you consider it a blocker, |
| 10 |
> > but perhaps to another person a blocker bug is something that completely |
| 11 |
> > destroys an installed Gentoo system. |
| 12 |
|
| 13 |
I was talking about severity, not priority, but I'll assume you were |
| 14 |
too. |
| 15 |
|
| 16 |
I usually work off the textual descriptions for each level of severity, |
| 17 |
which are provided by the guided bug reporting format |
| 18 |
(http://bugs.gentoo.org/enter_bug.cgi?format=guided). |
| 19 |
|
| 20 |
There's always going to be a level of subjectivity, but in this case the |
| 21 |
software failed during configure, and no fix could be found in either |
| 22 |
Bugzilla or the official project homepage. blocker is defined as "This |
| 23 |
bug prevents you from testing or developing the software" (again, in the |
| 24 |
guided format), which seems to match the problem reasonably well. |
| 25 |
|
| 26 |
If a bug "completely destroyed an installed Gentoo system", I'd say it |
| 27 |
qualifies as both critical ("the software crashes, hangs, or causes you |
| 28 |
to loose data") and blocker, so I guess some cases are hard to judge - |
| 29 |
you still wouldn't call that a normal bug, though :-) |
| 30 |
|
| 31 |
> > 4) If you want the assignees to pay attention to a bug, create some |
| 32 |
> > activity. Add a (polite!) comment requesting attention. That way the |
| 33 |
> > assignees get an email reminding them of its existence if they were |
| 34 |
> > concentrating on other things. |
| 35 |
|
| 36 |
Sorry, I should have mentioned in my email that I'd already made a |
| 37 |
comment on the bug. |
| 38 |
|
| 39 |
> The cause for concern in Andrew's case is that the bug was assigned to |
| 40 |
> an ex-developer, so it was not even likely to see any attention. DevRel |
| 41 |
> should look at the bugzilla accounts reassign bugs as part of a cleaning |
| 42 |
> process this week. |
| 43 |
|
| 44 |
Hmm, I should have thought of this - can I assume that |
| 45 |
http://www.gentoo.org/proj/en/devrel/roll-call/devlist.xml is the |
| 46 |
definitive list of current devs? In future, I'll check this before |
| 47 |
(somewhat erroneously) assuming the dev is no longer interested in |
| 48 |
working on the bug (although I was almost right...hehe) |
| 49 |
|
| 50 |
Thank you to both Donnie and Seemant for you replies. |
| 51 |
|
| 52 |
Also, thanks to Brian Jackson (iggy@g.o) for helping out with the |
| 53 |
bug in question. |
| 54 |
|
| 55 |
Keep up the good work, guys. |
| 56 |
|
| 57 |
Cheers |
| 58 |
|
| 59 |
Andrew |
| 60 |
|
| 61 |
|
| 62 |
-- |
| 63 |
gentoo-dev@g.o mailing list |
Archives