inactive issues
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 this action? (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 the counter-arguments). Lennart ___ cabal-devel mailing list cabal-devel@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/cabal-devel
Re: Cabal-1.22 keyed library filepaths
Hi Edward, On 9 February 2015 at 07:10, Edward Z. Yang ezy...@mit.edu wrote: Jens, could file a Cabal bug for the contents of this email? I opened https://github.com/haskell/cabal/issues/2437. Sorry for the delay, I was travelling and just saw your mail now. Thanks, Jens ___ cabal-devel mailing list cabal-devel@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/cabal-devel
Re: Looking for a new release manager for cabal
Hi, On 22 February 2015 at 14:01, Johan Tibell johan.tib...@gmail.com wrote: Hi, After about 3 years of cabal releases I'm looking for someone else to take over the responsibility as cabal release manager. Thank you for all your hard work managing Cabal releases during all this time. ___ cabal-devel mailing list cabal-devel@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/cabal-devel
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 ttue...@gmail.com wrote: On Tue, Feb 24, 2015 at 3:52 PM, lennart spitzner l...@informatik.uni-kiel.de 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 this action? (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 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 ___ cabal-devel mailing list cabal-devel@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/cabal-devel
Re: inactive issues
On Tue, Feb 24, 2015 at 3:52 PM, lennart spitzner l...@informatik.uni-kiel.de 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 this action? (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 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
