On Mon, 2009-04-27 at 18:30 -0700, John Poelstra wrote:
Adam Williamson said the following on 04/22/2009 03:00 PM Pacific
> Hi, guys. Just a general issue mail for Bugzappers: I've recently been
> talking to Seth Vidal, who wants special treatment for bugs in
> components he maintains (yum and createrepo): he's happy for them to be
> triaged according to the usual process, but he doesn't want the bugs
> changed from NEW to ASSIGNED.
How do you know which bugs you've triaged or not?
Set keyword or whiteboard to Triaged.
We originally killed it because we thought there was no way to track
every unique way of triaging bugs that each developer might want.
That is difficult, but I don't think we should decide not to try. We
really need to be bending over backwards to help developers, because if
we're not helping developers, we're not doing anything useful. Helping
developers is the entire point of triage.
that we moved to the newer model whereby individual triagers triage bugs
for specific components only.
Significant divergences from the policy requested by maintainers should
still be noted somewhere public and consistent, this is just good sense;
it saves effort when a triager joins the group triaging a given
component, or a handoff takes place, or whatever. "You and I just know
about this but no-one else does" is never a good system...
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org