[RELEASE] Apache Cassandra 3.0.6 released

2016-05-13 Thread Jake Luciani
The Cassandra team is pleased to announce the release of Apache Cassandra version 3.0.6. Apache Cassandra is a fully distributed database. It is the right choice when you need scalability and high availability without compromising performance. http://cassandra.apache.org/ Downloads of source an

Re: [VOTE] Release Apache Cassandra 3.6

2016-05-13 Thread Philip Thompson
I've run the upgrade tests against both 3.4 and 3.5, and I have not seen the new issues filed. This doesn't guarantee they are 3.6 regressions, but they may be. On Fri, May 13, 2016 at 5:59 AM, Aleksey Yeschenko wrote: > Seconding the -1 (binding) for the same reasons. > > -- > AY > > On 12 May

3.6 regressions

2016-05-13 Thread Jake Luciani
I've pushed a temporary cassandra-3.6 branch for the regressions found during the vote. ONLY regression fixes should go into that branch. Everyone else should ignore it (*Don't* merge from 3.0-> 3.6 -> 3.7). Regression fixes should go 3.6 -> 3.7 -> trunk -Jake

[VOTE RESULT] Release Apache Cassandra 3.0.6

2016-05-13 Thread Jake Luciani
With 6 binding +1, 6 non-binding +1 and no -1 the vote has passed. On Thu, May 12, 2016 at 9:13 AM, Gary Dusbabek wrote: > +1 > > On Tue, May 10, 2016 at 8:54 PM, Jake Luciani wrote: > > > I propose the following artifacts for release as 3.0.6. > > > > sha1: 52447873a361647a5e80c547adea9cf5ee85

[VOTE RESULT] Release Apache Cassandra 3.6

2016-05-13 Thread Jake Luciani
With this binding -1 the vote has failed. Will re-vote once issues are fixed. On Fri, May 13, 2016 at 5:59 AM, Aleksey Yeschenko wrote: > Seconding the -1 (binding) for the same reasons. > > -- > AY > > On 12 May 2016 at 23:44:46, Tyler Hobbs (ty...@datastax.com) wrote: > > Based on CASSANDRA-1

Re: [VOTE] Release Apache Cassandra 3.6

2016-05-13 Thread Aleksey Yeschenko
Seconding the -1 (binding) for the same reasons. --  AY On 12 May 2016 at 23:44:46, Tyler Hobbs (ty...@datastax.com) wrote: Based on CASSANDRA-11613 (and CASSANDRA-11760), I'm changing my vote to a (non-binding) -1. There is a legit regression in upgrading non-frozen UDTs that needs to be fi