Re: inactive issues

Good question. These issues were closed on my request. I've done similar clean-ups in the past. The issue tracker has gotten to large to be effective in help guide our work. We need to clean it up. In addition, lots of these issues weren't linked to the original reporter, making it less likely that the original reporter would step up with more information if needed, etc. On Tue, Feb 24, 2015 at 11:12 PM, Thomas Tuegel wrote:

...

hi,

i noticed today's run at the closing "inactive" issues on the tracker. i would like to to ask an innocent question: what exactly is the benefit of

...

(i disclose that it seems to me that valid, if inactive, issues are being closed, which i do not like. but before complaining, i want to know

On Tue, Feb 24, 2015 at 3:52 PM, lennart spitzner wrote: this action? the

...

counter-arguments).

The most important reason is that we do not now, nor will we ever, have the human resources to fix all those issues. When we have done this before, we usually get a few people who chime in about an issue that still affects them. This allows us to prioritize on issues that cause actual developers actual problems. It also lets us find these issues; there are still valid issues back there, on Page 28 of our GitHub issue tracker, but I know I never venture back there.

If an issue was closed that still causes you problems, you should by all means request that it be reopened.

-- Thomas Tuegel _______________________________________________ cabal-devel mailing list cabal-devel@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/cabal-devel