Re: Closing bugs with bad stack trace as INCOMPLETE

["Pedro Villavicencio Garrido" <pvillavi gmail com>]

2007/4/27, Vincent Untz <vuntz gnome org>:
> Hi,
>
> With the new bug-buddy, we're all receiving tons of new bugs. It's good,
> since we now know about some crashers we didn't know before.
>
> However, many of those bugs have invalid stack trace, and have been
> created by a user who might never go to bugzilla. We're marking those
> bugs as NEEDINFO, and we now have tons of NEEDINFO bugs. One issue I
> have with this is that in the past, I used to use NEEDINFO to mark some
> bugs that were definitely good bugs but which were just lacking an
> important information. It's not possible to easily find these bugs
> anymore, since they're lost in the mass of "BADSTACKTRACE" bugs.
>
> I'd like us to fix this. I see two possibilities: either introduce a new
> BADSTACKTRACE status, similar to NEEDINFO but only about incomplete
> stack traces, or decide that it's okay for us to close the bugs as
> INCOMPLETE and reopen them if the reporter comes with more details.
> This second option is probably easier.
>
> What do you think?

As not too many reporters provide a second  trace and for instance if
they do probably they gonna open a new bug with the new and complete
stack trace, so  I really think is a better to mark/close them as
INCOMPLETE and just modified the  stock response for badstacktrace.

Regards,

pedro.