1 |
On Fri, 2004-04-02 at 19:48, Andrew Ross wrote: |
2 |
> > The problems is that the original reporter didn't set the bug's severity |
3 |
> > properly, and I can't correct it because I'm not "the owner or submitter |
4 |
> > of the bug, or a sufficiently empowered user". |
5 |
> > |
6 |
> > This leaves me in a pickle - I don't want to file a duplicate bug, but I |
7 |
> > feel that the lack of activity on the bug may be, in part, due to its |
8 |
> > low severity (it should be blocker, but is rated normal). |
9 |
> > |
10 |
> > Would it be appropriate to reassign the bug to bug-wranglers and request |
11 |
> > the severity upgrade? The bug has been open since 2003-08-17 and the |
12 |
> > only comments are from users reporting similar problems, so I assume the |
13 |
> > dev isn't interested in working on the problem (or doesn't have the time). |
14 |
|
15 |
Here's a few suggestions, based on personal experience: |
16 |
|
17 |
1) Not all developers use or care about the priority. Your assumption is |
18 |
just that. |
19 |
|
20 |
2) Let the developers set the priorities. They know (or should know) |
21 |
what's important and what's not. Some of them will get annoyed if people |
22 |
screw around with the priorities after they have been set. |
23 |
|
24 |
3) Priority is a very subjective issue. Sure, you consider it a blocker, |
25 |
but perhaps to another person a blocker bug is something that completely |
26 |
destroys an installed Gentoo system. |
27 |
|
28 |
4) If you want the assignees to pay attention to a bug, create some |
29 |
activity. Add a (polite!) comment requesting attention. That way the |
30 |
assignees get an email reminding them of its existence if they were |
31 |
concentrating on other things. |
32 |
|
33 |
Thanks, |
34 |
-- |
35 |
Donnie Berkholz |
36 |
Gentoo Linux |