Thanks for the feedback all. For the previous listed reasons, I'll swap
to a -1 vote, too.
I count 2 binding +1, 3 binding -1, and 3 non-binding -1 votes.
Since cassandra-3.11 was branched last week for fixes on top of 3.10, it
seems that the next 3.10 candidate could just come from the
cassandra
Thanks for all the feedback, I'm changing to a -1, too.
Vote comes to 1 binding +1, 3 binding -1, 3 non-binding -1.
--
Kind regards,
Michael
On 11/08/2016 02:09 PM, Michael Shuler wrote:
> I propose the following artifacts for release as 3.10.
>
> sha1: 072b5271a88328b909b230d0e30df1c7476fdb3f
I am changing my vote to -1 and closing this vote for the regression
reported in CASSANDRA-12867 by Kurt Greaves.
For the record, I count 2 binding (1 non-binding) +1 votes and 3 binding
(1 non-binding, counting Kurt) -1 votes.
I've marked CASSANDRA-12867 as Critical with fixver=3.10,3.0.10, so h