Re: [VOTE RESULT] Release Apache Cassandra 3.8

2016-07-26 Thread Brandon Williams
Small nit: there are currently 5 binding +1 and 1 binding -1, (or 2, with Jonathan.) On Tue, Jul 26, 2016 at 5:42 PM, Aleksey Yeschenko wrote: > Sorry, but I’m counting 3 binding +1s and 1 binding -1 (2, if you > interpret Jonathan’s emails as such). > > Thus, if you were to

Re: [VOTE RESULT] Release Apache Cassandra 3.8

2016-07-26 Thread Aleksey Yeschenko
Sorry, but I’m counting 3 binding +1s and 1 binding -1 (2, if you interpret Jonathan’s emails as such). Thus, if you were to do close the vote now, the vote is passing with the binding majority, and the required minimum # of +1s gained. I also don’t see the PMC consensus on ‘August 3.8 release

Re: [VOTE RESULT] Release Apache Cassandra 3.8

2016-07-26 Thread Aleksey Yeschenko
Sorry (: Only see yours, Dave’s, and mine in my client. Apparently I’ve trashed the email chain at some point. --  AY On 26 July 2016 at 23:48:49, Brandon Williams (dri...@gmail.com) wrote: Small nit: there are currently 5 binding +1 and 1 binding -1, (or 2, with Jonathan.) On Tue, Jul

Re: [VOTE RESULT] Release Apache Cassandra 3.8

2016-07-26 Thread Brandon Williams
For completeness, Jake and Pavel are the other two. On Tue, Jul 26, 2016 at 5:50 PM, Aleksey Yeschenko wrote: > Sorry (: Only see yours, Dave’s, and mine in my client. Apparently I’ve > trashed the email chain at some point. > > -- > AY > > On 26 July 2016 at 23:48:49,

Failing Tests 2016-07-26 [cassandra-3.9]

2016-07-26 Thread Josh McKenzie
So today's report looks a little rough. Had the following come up: - Extensive timeouts on testall. We've seen this before and a re-run usually resolves it. Do we think this might be a provisioning / hardware limitation problem? Are the tests too long / too close to the boundary on