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

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)

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)

-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)

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

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

We voted in the dev list discussion[1] that we wont cut a release till all unit tests are passing. I can see that testall are failing for trunk and 3.X. Hence I need to do a -1 on this release. My -1 is not due to Dtest failing as we discussed about unit tests only in that thread. I will start

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

We had decided in an email thread initiated by me that we won't cut releases till all tests are passing. Why not wait till these patches are merged? Is there any critical fix in it which need to be rushed out ? > On Nov 20, 2016, at 23:36, Oleksandr Petrov >

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

>From just a quick glance, I can say at least some of the tests are either PA or are getting there: For example: http://cassci.datastax.com/job/cassandra-3.X_novnode_dtest/lastCompletedBuild/testReport/paging_test/TestPagingData/test_paging_with_filtering_on_partition_key/ Should be fixed by

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

Hi, I see the following test runs are failing. Are they for this release? http://cassci.datastax.com/job/cassandra-3.X_utest_cdc/ http://cassci.datastax.com/job/cassandra-3.X_testall/ http://cassci.datastax.com/job/cassandra-3.X_offheap_dtest/

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

+1 On Sat, Nov 19, 2016 at 7:08 AM, Michael Shuler wrote: > I propose the following artifacts for release as 3.10. > > sha1: 96d67b109a2ef858c2753bbb9853d01460cb8f8e > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.10-tentative >

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

+1 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: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/3.10-tentative

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

+1 On 2016-11-18 10:08 (-0800), Michael Shuler wrote: > I propose the following artifacts for release as 3.10. > > sha1: 96d67b109a2ef858c2753bbb9853d01460cb8f8e > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.10-tentative >

[VOTE] Release Apache Cassandra 3.10 (Take 3)

I propose the following artifacts for release as 3.10. sha1: 96d67b109a2ef858c2753bbb9853d01460cb8f8e Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.10-tentative Artifacts: