Re: Attempt to Triage Bug 329386

[Elijah Newren <newren gmail com>]

On 2/11/06, Lex Hider <lexhider internode on net> wrote:
> On Sat, 2006-02-11 at 19:49 -0700, Elijah Newren wrote:
> >   I consider the new vs. unconfirmed
> > suckiness that currently exists to be a temporary situation.  One that
> > has lasted many years, granted, but one that will be killed sooner or
> > later.  And then my long diatribe on not confirming bugs will be
> > totally obsolete and wrong.  At long last.  :-)
>
> If that is the case, I find it surprising that you would discourage new
> bugsquad members from confirming bugs.

Why?  If it gets fixed in a way that I'd like (e.g. developers don't
get emails until either a certain amount of time has past or the
bugsquad has handled them first to ensure that they're not dupes or
obviously need more info), then confirming by the bugsquad would make
total sense.

Until then, I'm still of the opinion that it does more harm than good.

> > It also depends on the ability to have developers not be emailed for
> > unconfirmed bugs, an ability we don't yet have.  I think that's the
> > biggest obstacle.  I think we have sufficient manpower to push bugs
> > from unconfirmed to new in such a case where developers don't see the
> > unconfirmed bugs.
>
> I'd like to help if I can.

Install gnome bugzilla locally (basically, you follow the instructions
for setting up the real bugzilla, but you use a cvs checkout of the
bugzilla-newer module rather than a tarball of upstream bugzilla or a
cvs checkout of upstream bugzilla).  I had a more detailed guide to
this once that wouldn't make you try to read & follow & modify
upstream instructions all at the same time, but when I went to look
for it a couple months ago it appears to have been lost forever.  :( 
So sorry for the lame instruction but they'll have to do.  Anyway,
after you get it up and running, start patching it and submitting the
patches.  If you have questions on this, you can ask on IRC or
bugzilla-devel-list.  :)

Cheers,
Elijah