+ 1
This is a good idea.
-Original Message-
From: beggles...@apple.com [mailto:beggles...@apple.com]
Sent: Friday, September 15, 2017 8:29 AM
To: dev@cassandra.apache.org
Subject: Re: Proposal: Closing old, unable-to-repro JIRAs
+1 to that
On September 14, 2017 at 4:50:54 PM, Jeff
+1 to that
On September 14, 2017 at 4:50:54 PM, Jeff Jirsa (jji...@gmail.com) wrote:
There's a number of JIRAs that are old - sometimes very old - that
represent bugs that either don't exist in modern versions, or don't have
sufficient information for us to repro, but the reporter has gone awa
Jeff, fantastic idea. +1
John, i'd prefer to get the non-PA ones out of the way first. With PA,
someone at least tried to improve to software.
I'm not at a computer now, but it would be instructive to have a beak down
of those types of tickets by age. I can do that later.
Jason
On Thu, Sep 14, 2
I think it's a great idea. I'd like to do the same thing with the available
patches but I'm totally ok with doing that separately.
On Thu, Sep 14, 2017 at 4:50 PM Jeff Jirsa wrote:
> There's a number of JIRAs that are old - sometimes very old - that
> represent bugs that either don't exist in mod
+1, if it turns out that something is still valid/important, then people
can always re-open.
On Thu, Sep 14, 2017 at 4:50 PM, Jeff Jirsa wrote:
> There's a number of JIRAs that are old - sometimes very old - that
> represent bugs that either don't exist in modern versions, or don't have
> suffic
There's a number of JIRAs that are old - sometimes very old - that
represent bugs that either don't exist in modern versions, or don't have
sufficient information for us to repro, but the reporter has gone away.
Would anyone be offended if I start tagging these with the label
'UnableToRepro' or 'U
