1 |
On Fri, 2004-04-02 at 18:40, Donnie Berkholz wrote: |
2 |
|
3 |
> Here's a few suggestions, based on personal experience: |
4 |
> |
5 |
> 1) Not all developers use or care about the priority. Your assumption is |
6 |
> just that. |
7 |
> |
8 |
> 2) Let the developers set the priorities. They know (or should know) |
9 |
> what's important and what's not. Some of them will get annoyed if people |
10 |
> screw around with the priorities after they have been set. |
11 |
> |
12 |
> 3) Priority is a very subjective issue. Sure, you consider it a blocker, |
13 |
> but perhaps to another person a blocker bug is something that completely |
14 |
> destroys an installed Gentoo system. |
15 |
> |
16 |
> 4) If you want the assignees to pay attention to a bug, create some |
17 |
> activity. Add a (polite!) comment requesting attention. That way the |
18 |
> assignees get an email reminding them of its existence if they were |
19 |
> concentrating on other things. |
20 |
> |
21 |
> Thanks, |
22 |
|
23 |
The cause for concern in Andrew's case is that the bug was assigned to |
24 |
an ex-developer, so it was not even likely to see any attention. DevRel |
25 |
should look at the bugzilla accounts reassign bugs as part of a cleaning |
26 |
process this week. |
27 |
|
28 |
Thanks, |
29 |
-- |
30 |
Seemant Kulleen |
31 |
Developer and Project Co-ordinator, |
32 |
Gentoo Linux http://dev.gentoo.org/~seemant |
33 |
|
34 |
Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x3458780E |
35 |
Key fingerprint = 23A9 7CB5 9BBB 4F8D 549B 6593 EDA2 65D8 3458 780E |