Yeah, the number of users running 2.1 was part of my concern, and if
we're happy to maintain 4 actively supported branches, along with trunk,
I think that's fine.

A 2.1.18 release with the few fixes committed in cassandra-2.1 will at
least be an opportunity to get RPMs rolled up for users in all branches.

I appreciate the feedback.

-- 
Michael

On 06/21/2017 12:01 AM, Jeff Jirsa wrote:
> Site says: 
> 
>   * Apache Cassandra 2.1 is supported until 4.0 release (date
>     TBD) with critical fixes only.
> 
> Since we don't know when 4.0 goes out, we shouldn't be in a hurry to do
> a final 2.1.18 cut. There's not much in that branch (a few 2i fixes,
> some build fixes, a cqlsh fix, and a logging fix), so no reason to cut
> it now, and certainly no reason to cut a "final" release now. Leave it
> open, there's no real cost to having it open, and if a real critical bug
> pops up between now and 4.0, the hundreds/thousands of people running
> 2.1 in prod will appreciate a fix.
> 
> - Jeff
> 
> 
> 
> On Tue, Jun 20, 2017 at 8:20 PM, Michael Shuler <mich...@pbandjelly.org
> <mailto:mich...@pbandjelly.org>> wrote:
> 
>     Sounds good to me - I'll work up a 2.2.10 artifact set tomorrow.
> 
>     Looking at our current branches and the EOL TBD dates on the download
>     page, I believe the 4.0 references for sunsetting branches was prior to
>     considering a 3.11.0 release with ongoing support for the branch.
> 
>     Should we also do a 2.1.18 release as a final cut and end commits to the
>     cassandra-2.1 branch? I'm sorry I hadn't thought about this sooner.
> 
>     Michael
> 
>     On 06/20/2017 09:11 PM, Nate McCall wrote:
>     > Since we have the others going out and we do have some bugfixes there.
> 
>     ---------------------------------------------------------------------
>     To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
>     <mailto:dev-unsubscr...@cassandra.apache.org>
>     For additional commands, e-mail: dev-h...@cassandra.apache.org
>     <mailto:dev-h...@cassandra.apache.org>
> 
> 


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

Reply via email to