[Bugsquad] [Bug 284524] nspluginviewer crashed when encountered a swf file
Andre Klapper
ak-47 at gmx.net
Sat Jul 21 21:39:30 UTC 2012
On Wed, 2012-06-20 at 18:42 -0400, "Gérard Talbot" wrote:
> > Myriam Schweingruber <myriam at kde.org> changed:
> >
> > What |Removed |Added
> > ----------------------------------------------------------------------------
> > Status|UNCONFIRMED |RESOLVED
> > Version|unspecified |4.4.5
> > Resolution|--- |INVALID
> >
> > --- Comment #3 from Myriam Schweingruber <myriam at kde.org> ---
> > Closing for lack of feedback. Feel free to reopen if you can reproduce
> > this
> > with Konqueror 4.8.4 or later and provide the necessary feedback.
>
> Myriam,
>
> I do not object to your decision; I agree with your decision.
+1.
In case developers maintain ToDo lists outside of Bugzilla because
Bugzilla is full of ancient useless reports that pop up in search
results, then it's a sign that Bugzilla is not in a good state. In my
very humble opinion this is a problem that Mozilla now have in their
Bugzilla. Hence too many reports and no aggressive triaging might
require (semi-) automatical closing of tickets after a certain time in
bigger projects.
> Retrospectively speaking, I think bugs.kde.org should create another
> Resolution field so that we could close a bug report for/due to lack of
> response. Mozilla.org and connect's IE beta feedback created a similar
> resolution field/option when bug reports were unconfirmable, unactionable
> and when the bug reporter did not reply to NEEDMOREINFO types of comments.
For the records and to compare to other projects:
In bugzilla.mozilla.org normally RESOLVED WORKSFORME (if not
reproducible) or RESOLVED INVALID (if report is way too vague) is used
in such cases, but there is no NEEDINFO state (instead the whiteboard is
sometimes used by adding a "[closeme-2012-08-31]" style entry, rather
inconsequently IMO).
bugzilla.gnome.org normally uses RESOLVED INCOMPLETE if no answer was
provided by the reporter after setting to NEEDINFO state.
andre
--
mailto:ak-47 at gmx.net | failed
http://blogs.gnome.org/aklapper
More information about the Bugsquad
mailing list