Closing old idle bugs?
Jeroen van Meeuwen (Kolab Systems)
vanmeeuwen at kolabsys.com
Mon Aug 2 21:41:49 EDT 2010
Bron Gondwana wrote:
> On Mon, Aug 02, 2010 at 05:10:26PM +0200, Jeroen van Meeuwen (Kolab Systems)
> > Hi there,
> > would it be acceptable if old, idle bugs in bugzilla were closed after due
> > consideration?
> That would be a great idea!
> > For example, I encounter bug #2590 with status NEW; I would like to
> > it to clean up the bug database, possibly only after requesting some
> > (like I did with this one).
> >  https://bugzilla.andrew.cmu.edu/show_bug.cgi?id=2590
> Maybe we should do a bug cleaning week? I'm on leave at the moment. I
> we should probably go through all the bugs as a group and decide on their
> status and applicability. I suspect quite a few of them are no longer valid
> or already solved - just not updated.
It seems that I do not have any permissions to change a bug's status; I have a
> Perhaps if we posted one email per bug to the mailing list and asked for a
> discussion on its merits. Maybe not all at once so they don't get lost in
> haze, but we could group them up.
One bug a day through the list would be very inefficient, and I'm sure there's
bugs that actually do deserve love & attention. There's a number of bugs that
have been resolved already, just haven't been closed. Let's remember that if a
bug is closed while not satisfactory to the reporter, the bugs can simply be
Most of them look like they just need some follow-up and can be closed in
2/4/6 weeks if no response has been given to any inquiries for more
information (like #2590, the time window is a project choice of course).
Jeroen van Meeuwen
Senior Engineer, Kolab Systems AG
e: vanmeeuwen at kolabsys.com
t: +316 42 801 403
pgp: 9342 BF08
More information about the Cyrus-devel