Re: Bug reporting [Was: Promoting greater integration between testers!:)]

[Owen Taylor <otaylor redhat com>]

On Mon, 2003-06-30 at 15:27, Luis Villa wrote:
> On Mon, 2003-06-30 at 15:16, Owen Taylor wrote:
> > On Mon, 2003-06-30 at 14:53, Jeff Waugh wrote:
> > > <quote who="Owen Taylor">
> > > 
> > > > Fromthe GTK+ bug perspective I hate the idea of one more
> > > > step to deal with incoming bug reports ...
> > > 
> > > You can RESOLVE/WONTFIX an UNCONFIRMED bug, so it won't be an additional
> > > step unless you begin to avoid looking through UNCONFIRMED bugs as part of
> > > your developer-side process.
> > 
> > The point is not that we can't close bugs without confirming them, 
> > but that a great deal of incoming bugs for GTK+ *are* not immediate
> > closed. There are three approaches we could take:
> > 
> >  A) Just blanket confirm all GTK+ bugs periodically
> >  B) Try to decide on some objective criterion for confirming
> >     a GTK+ bug. (Picking some random recent bug, what would you
> >     say for http://bugzilla.gnome.org/show_bug.cgi?id=116364?)
> >  C) Just leave bugs UNCONFIRMED
> > 
> > A) and B) are extra work, C) is aesthetically unappealing.
> 
> For all intents and purposes, you review and milestone every bug, right?
> If that's the case, the difference between a bug being UNCONFIRMED and
> being new and unmilestoned would be (for GTK) very minimal. 

Yes, I'm basically complaining about one extra mouse click when
milestoning bugs. "GTK+ Grouch" has a nice alliterative ring
to it, no?

Well perhaps slightly more substantively, my concern is that
separating out "is this reporter smoking something, or is
it a real issue" from  "so, what do we do about it?" is an
extra step that I'd rather not worry about. 

Now, that can be dealt with by policy of what UNCONFIRMED means, 
but perhaps bug reporters will wonder if they see a couple
of people commenting on their bug while it sits in the
UNCONFIRMED state. 

Anyways, don't let me block action in this area if someone wants
to work on it. We already have a few UNCONFIRMED bugs coming in 
for GTK+ from bug-buddy so it's nothing terribly new. (*)

Regards,
						Owen

(*) Reference to previous rants about how bug-buddy interacts
with bugzilla.