[prev in list] [next in list] [prev in thread] [next in thread] 

List:       cassandra-dev
Subject:    RE: Proposal: Closing old, unable-to-repro JIRAs
From:       "Tyagi, Preetika" <preetika.tyagi () intel ! com>
Date:       2017-09-15 16:28:29
Message-ID: 4397857C7F0B614083071599C4F2366C0100446427 () ORSMSX105 ! amr ! corp ! intel ! com
[Download RAW message or body]

+ 1 

This is a good idea.

-----Original Message-----
From: beggleston@apple.com [mailto:beggleston@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 Jirsa (jjirsa@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 away. 

Would anyone be offended if I start tagging these with the label 'UnableToRepro' or \
'Unresponsive' and start a 30 day timer to close them?  Anyone have a better \
suggestion? 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
For additional commands, e-mail: dev-help@cassandra.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]