Feedback wanted: Change INVALID resolution to NOTABUG in bugs.kde.org

[Matt Rogers]

On Sunday 22 February 2009 06:25:27 George Goldberg wrote:
> On Sat, Feb 21, 2009 at 6:40 PM, Lydia Pintscher <lydia at kde.org> wrote:
> > On Sat, Feb 21, 2009 at 18:49, Matt Rogers <mattr at kde.org> wrote:
> >> Hi,
> >>
> >> Since we're using INVALID mostly to indicate something is not a bug in
> >> KDE itself, I'd like to change the INVALID resolution to NOTABUG to
> >> better indicate this. We also have other resolutions such as UPSTREAM
> >> and DOWNSTREAM which means INVALID isn't really used for those either.
> >>
> >> The creation of duplicate repports (i.e. one right after the other)
> >> should be gone. Bugzilla added code upstream to prevent that from
> >> happening and I've used the same code in the wizard.
> >>
> >> If there are no objections, I'll make the change early Monday morning.
> >
> > At Amarok we mostly use INVALID to close crash reports without debug
> > symbols. We kindly ask the reporter to install them/recompile and
> > reopen the report when they have a useful backtrace. What would we do
> > with those bugs? (Leaving them open is not an option.)
>
> The solution to this problem is something I and other people have been
> asking for for over a year now (although no resounding agreement seems
> to have come that it should be done).
>
> There should be a bug state called NEEDINFO, and a resolution state
> called TIMEDOUT (or something similar).
>
> Basically, if a bug is missing necessary info, like a useless
> backtrace, it could be put into the NEEDINFO state with a comment
> added telling the user whats needed. Then if no information is
> provided within a reasonable time, it could be RESOLVED->TIMEDOUT.
> This is much clearer and sounds less agressive than just slapping an
> INVALID tag on it.
>
>
> --
> George Goldberg

NEEDSINFO as a resolution is coming. I'm just working through my TODO list on 
bugzilla related things.
--
Matt