Re: [VOTE] Release Apache Cassandra 3.10 (Take 3)

2016-11-25 Thread Brandon Williams
I'll change to binding -1 for the reasons previously listed. On Fri, Nov 18, 2016 at 12:08 PM, Michael Shuler wrote: > I propose the following artifacts for release as 3.10. > > sha1: 96d67b109a2ef858c2753bbb9853d01460cb8f8e > Git: >

Re: [VOTE] Release Apache Cassandra 3.10 (Take 3)

2016-11-25 Thread Paulo Motta
non-binding -1 as well, it seems CASSANDRA-12905 can prevent bootstrap of nodes with MV so it would be nice to release 3.10 with that fix 2016-11-25 15:04 GMT-02:00 Jonathan Haddad : > -1 (non-binding) for the failing tests as well. > > On Fri, Nov 25, 2016 at 10:35 AM Sam

Re: [VOTE] Release Apache Cassandra 3.10 (Take 3)

2016-11-25 Thread Jonathan Haddad
-1 (non-binding) for the failing tests as well. On Fri, Nov 25, 2016 at 10:35 AM Sam Tunnicliffe wrote: > I'll register another (non-binding) -1 due to the failing tests. In > particular, CASSANDRA-12651 is due to a legit bug with potential corruption > and data loss (albeit in

Re: [VOTE] Release Apache Cassandra 3.10 (Take 3)

2016-11-25 Thread Sam Tunnicliffe
I'll register another (non-binding) -1 due to the failing tests. In particular, CASSANDRA-12651 is due to a legit bug with potential corruption and data loss (albeit in indexes only). The same bug is also the likely cause of CASSANDRA-12590, so it'd be good to include the fix in 3.10. On Mon, Nov