List Archive: gentoo-dev
Note: Due to technical difficulties, the Archives are currently not up to date.
provides an alternative service for most mailing lists.c.f. bug 424647
On Fri, 2004-04-02 at 18:40, Donnie Berkholz wrote:
> Here's a few suggestions, based on personal experience:
> 1) Not all developers use or care about the priority. Your assumption is
> just that.
> 2) Let the developers set the priorities. They know (or should know)
> what's important and what's not. Some of them will get annoyed if people
> screw around with the priorities after they have been set.
> 3) Priority is a very subjective issue. Sure, you consider it a blocker,
> but perhaps to another person a blocker bug is something that completely
> destroys an installed Gentoo system.
> 4) If you want the assignees to pay attention to a bug, create some
> activity. Add a (polite!) comment requesting attention. That way the
> assignees get an email reminding them of its existence if they were
> concentrating on other things.
The cause for concern in Andrew's case is that the bug was assigned to
an ex-developer, so it was not even likely to see any attention. DevRel
should look at the bugzilla accounts reassign bugs as part of a cleaning
process this week.
Developer and Project Co-ordinator,
Gentoo Linux http://dev.gentoo.org/~seemant
Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x3458780E
Key fingerprint = 23A9 7CB5 9BBB 4F8D 549B 6593 EDA2 65D8 3458 780E
signature.asc (This is a digitally signed message part)