Re: Opting out of bugsquad for my modules

["Diego Escalante Urrelo" <diegoe gnome org>]

Hey again,

First I confess I haven't read the bugsquad wiki deeply so I might be
suggesting something that's already done.
Now, reading this thread it sounds to me like a set of suggestions for
general triaging. If you agree we could put this on the wiki.

It would be nice to have others opinion or comment on their work flow
so we can give new triagers a better overview of things.
So far the following has been suggested:

> > On 1/2/08, Bruno Boaventura <brunoboaventura gmail com> wrote:
> > > Sorry, Behdad. I think I did it sometimes too, when I was starting.
> > > Maybe can we have something more specifically about this on
> > > http://live.gnome.org/Bugsquad/TriageGuide? BTW, I recommend new
> > > triagers do not close any bug as INCOMPLETE when it have a stacktrace
> > > and (comments > 1).
> > >
> > > Bugsquaders: Ideas?
> > >
> >

> On Wed, 2008-01-02 at 14:39 -0500, Diego Escalante Urrelo wrote:
> > Hey,
> >
> > Usually I close as INCOMPLETE when the reporter is a random email
> > address with 0 points and comment-less. I also check if the trace can
> > be read or if it's just a ton of ?? that doesn't even let you guess
> > what's the real crash.
>

On 1/2/08, Behdad Esfahbod <behdad behdad org> wrote:
> What I want to see is:
>
>   - No bug with dups closed INCOMPLETE
>   - No bug with comments closed INCOMPLETE
>   - When a Simple dup search shows a trace is a dup of an INCOMPLETE
> bug, the INCOMPLETE is REOPENED and the dup added
>
> That way, I can feel confident that a real but infrequent crasher in my
> software doesn't go unnoticed just because all the reports were closed
> INCOMPLETE.
>