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

2017-01-27 Thread Michael Shuler
Thanks, Sylvain! -- Michael On 01/27/2017 02:33 AM, Sylvain Lebresne wrote: > Fyi, I just committed CASSANDRA-13025 so it's ready for a re-roll as far as > I can tell. > > On Tue, Jan 24, 2017 at 12:31 AM, Michael Shuler > wrote: > >> This vote is being failed for

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

2017-01-27 Thread Sylvain Lebresne
Fyi, I just committed CASSANDRA-13025 so it's ready for a re-roll as far as I can tell. On Tue, Jan 24, 2017 at 12:31 AM, Michael Shuler wrote: > This vote is being failed for CASSANDRA-13058 (committed after tentative > tag) and CASSANDRA-13025 (patch available). > >

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

2017-01-23 Thread Michael Shuler
This vote is being failed for CASSANDRA-13058 (committed after tentative tag) and CASSANDRA-13025 (patch available). Vote count was 5 binding +1, 1 binding -1, and one non-binding -1. I'll re-roll a "Take 5" when CASSANDRA-13025 gets committed, tests appear stable, and we'll try again. -- Kind

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

2017-01-23 Thread Nate McCall
Indeed I conflated the two - thanks Sylvain. On Mon, Jan 23, 2017 at 11:19 PM, Sylvain Lebresne wrote: > On Mon, Jan 23, 2017 at 2:31 AM, Nate McCall wrote: > >> What was the resolution on this? >> >> Looks like we resolved/Fixed CASSANDRA-13058. Can we

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

2017-01-23 Thread Sylvain Lebresne
On Mon, Jan 23, 2017 at 2:31 AM, Nate McCall wrote: > What was the resolution on this? > > Looks like we resolved/Fixed CASSANDRA-13058. Can we re-roll and go again? > As I mentioned, CASSANDRA-13025 is also a regression and should be fix before we re-roll. It's ready for

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

2017-01-22 Thread Nate McCall
What was the resolution on this? Looks like we resolved/Fixed CASSANDRA-13058. Can we re-roll and go again? On Tue, Jan 17, 2017 at 4:26 AM, Sylvain Lebresne wrote: > I'm a bit sorry about it, but I'm kind of -1 on the account of >

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

2017-01-16 Thread Sylvain Lebresne
I'm a bit sorry about it, but I'm kind of -1 on the account of https://issues.apache.org/jira/browse/CASSANDRA-13025. It's a genuine regression during upgrade that we should really fix before it's released in the wild. I apologize for not having bump the priority on this ticket sooner but I think

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

2017-01-15 Thread Paulo Motta
-1 since CASSANDRA-13058 introduces a regression that prevents successful decommission when the decommissioning node has hints to transfer. While this is relatively minor and there is a workaround (force hint replay before decommission),

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

2017-01-14 Thread Jeff Jirsa
+1 -- Jeff Jirsa > On Jan 13, 2017, at 4:46 PM, Michael Shuler wrote: > > I propose the following artifacts for release as 3.10. > > sha1: 9c2ab25556fad06a6a4d58f4bb652719a8a1bc27 > Git: >

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

2017-01-14 Thread Brandon Williams
+1 On Fri, Jan 13, 2017 at 6:46 PM, Michael Shuler wrote: > I propose the following artifacts for release as 3.10. > > sha1: 9c2ab25556fad06a6a4d58f4bb652719a8a1bc27 > 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 4)

2017-01-14 Thread Nate McCall
> I propose the following artifacts for release as 3.10. > +1 Thanks!

[VOTE] Release Apache Cassandra 3.10 (Take 4)

2017-01-13 Thread Michael Shuler
I propose the following artifacts for release as 3.10. sha1: 9c2ab25556fad06a6a4d58f4bb652719a8a1bc27 Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.10-tentative Artifacts: