Re: [VOTE] Release Apache Cassandra 3.11.2

2018-02-12 Thread kurt greaves
May as well just recut and include it IMO. Sure, the issue is work-aroundable, but in a pretty terrible way. Only a few hours will be lost (sorry Michael :/)​

Re: [VOTE] Release Apache Cassandra 3.11.2

2018-02-12 Thread Nate McCall
I thought we had committed CASSANDRA-14212 last week. We need a release bad enough that I don't want to sink this with a -1, but we have seen this be an issue with folks a couple of times recently. On Tue, Feb 13, 2018 at 10:16 AM, Jon Haddad wrote: > I’m a +1 on getting

Re: [VOTE] Release Apache Cassandra 3.11.2

2018-02-12 Thread Jon Haddad
I’m a +1 on getting this into 3.11.2. > On Feb 12, 2018, at 1:11 PM, mck wrote: > >> I propose the following artifacts for release as 3.11.2. >> … >> The vote will be open for 72 hours (longer if needed). > > > I just pushed the back-port of CASSANDRA-13080 (under

Re: [VOTE] Release Apache Cassandra 3.11.2

2018-02-12 Thread mck
> I propose the following artifacts for release as 3.11.2. > … > The vote will be open for 72 hours (longer if needed). I just pushed the back-port of CASSANDRA-13080 (under CASSANDRA-14212). This is the improvement "Use new token allocation for non bootstrap case as well". We've seen that this

Re: [VOTE] Release Apache Cassandra 3.11.2

2018-02-12 Thread Brandon Williams
+1 On Mon, Feb 12, 2018 at 2:31 PM, Michael Shuler wrote: > I propose the following artifacts for release as 3.11.2. > > sha1: f6ec5c5d18c2900af0ef6e314edbd19aaa682a55 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= >

Re: [VOTE] Release Apache Cassandra 3.11.2

2018-02-12 Thread Nate McCall
> I propose the following artifacts for release as 3.11.2. > +1 - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org