[racket-dev] Responding to old bug reports

From: Matthew Flatt (mflatt at cs.utah.edu)
Date: Thu Dec 1 11:22:39 EST 2011

How about closing the PR, but with a message that says we would be
happy to reopen if we've closed the PR by mistake (i.e., there's still
a problem) or if more information is available?

At Thu, 1 Dec 2011 11:13:23 -0500, Sam Tobin-Hochstadt wrote:
> In my role as bug czar, I've been trying to work through the backlog
> of old unexamined bugs.  Unfortunately, many of them (a) have very
> little information and (b) are from a long time ago.  A good example
> is this one: http://bugs.racket-lang.org/query/?cmd=view&pr=9481
> There are a few options here:
> 1. Close old (how old?) bugs that don't have enough information to
> triage/reproduce.
> 2. Put them in the "feedback" state, with a general request for more
> information.
> 3. Attempt to guess at what component this belongs to, and assign it that way.
> 4. Leave it in the current state.
> I think 3 and 4 are both unacceptable. I'm leaning toward 2.  The
> major drawback of 2 vs 1 is that we accumulate lots of bugs that
> nothing will ever happen with. The major drawback of 1 is that we're
> saying to someone who took the time to report a bug "we didn't care
> about this bug at the time, so now we're closing it".
> Thoughts?
> -- 
> sam th
> samth at ccs.neu.edu
> _________________________________________________
>   For list-related administrative tasks:
>   http://lists.racket-lang.org/listinfo/dev

Posted on the dev mailing list.