lsp at informatik.uni-kiel.de
Wed Feb 25 18:21:02 UTC 2015
I am not convinced. how does closing ~40 out of ~700 open tickets make
the contributors more effective? that demand exceeds resources is
true, but it is no argument for closing issues. many of the issues
represent sensible ideas for features that do not need new feedback.
I'd say the general lack of stability and the recently mentioned
lack of tests are the main problems of Cabal;
to a degree this looks like shooting at symptoms.
But there is no need to convince me; there is need to priotize and
my doubts are low priority at best.
feel free to reply, but i'll try to shut up now :)
On 25/02/15 08:09, Johan Tibell wrote:
> Good question.
> These issues were closed on my request. I've done similar clean-ups in the
> 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 <ttuegel at gmail.com> wrote:
>> On Tue, Feb 24, 2015 at 3:52 PM, lennart spitzner
>> <lsp at informatik.uni-kiel.de> wrote:
>>> 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 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 at haskell.org
More information about the cabal-devel