on further consultation [gnome2 triage process]

[Luis Villa <louie ximian com>]

So... it appears that using milestones as I'd proprosed would introduce
difficulties for both nautilus and gtk. Since they account for about 1/2
of the open bugs in the core of gnome, any plan that doesn't work for
them is not going to work, period. So... we'll use keywords :) I'll
leave the proposed milestones in the bugzilla in case some projects find
them useful.

So, a brief overview of what I'm proposing wrt keywords. I'm definitely
open to adding more later; thankfully, they're a touch easier to add
(even if they are harder to use consistently. :/

GNOME2: if a bug is either against a GNOME2 build/port/whathaveyou, or
if it is against a 1.[0|2|4] product and still relevant, it should get
the GNOME2 keyword. We'll use this for reporting on the state of GNOME2.
This is the key one, really.

MUSTFIX/SHOULDFIX: These are from Telsa's original proposal. I'd like to
scrap them whereever possible in favor of
blocker/critical/immediate/urgent severities and priorities, as per the
original proposal. If using these standards are going to conflict with
(for example) nautilus's own triage, we can work something out using
these keywords, but I'd prefer to stay away from them for now.

PLEASEFIX: I won't use this formally myself, but I will encourage
volunteers to use this to nominate a bug for consideration for 2.0, even
if the priority/severity are not high.

At some point we'll probably have to ponder using something to indicate
'future' or '2.x' but for the moment it seems reasonable to stick with
just using GNOME2 for consistency and then work from there as we get a
bit closer to release and the triage picture shapes up.

So, that's it for now. Again, feedback wanted and welcome.
Luis



_______________________________________________
gnome-hackers mailing list
gnome-hackers gnome org
http://mail.gnome.org/mailman/listinfo/gnome-hackers