The main issue reported in CASSANDRA-11765 <https://issues.apache.org/jira/browse/CASSANDRA-11765> was fixed by CASSANDRA-11763 <https://issues.apache.org/jira/browse/CASSANDRA-11763>.
The patch for CASSANDRA-11765 is for a new issue, that doesn't look like a regression of 3.6. On Wed, Jun 1, 2016 at 7:43 PM, Jim Witschey <jim.witsc...@datastax.com> wrote: > DataStax' Cassandra Test Engineering Team recommends that voters be > aware of CASSANDRA-11663 and CASSANDRA-11765 when they vote: > > https://issues.apache.org/jira/browse/CASSANDRA-11663 > https://issues.apache.org/jira/browse/CASSANDRA-11765 > > As mentioned in our report (https://goo.gl/hNyrnW), CASSANDRA-11663 > may have been addressed by the fix for a resolved ticket, and > CASSANDRA-11765 is currently marked Patch Available. Please see the > report for more details. > -- [image: datastax_logo.png] <http://www.datastax.com/> Stefania Alborghetti Apache Cassandra Software Engineer |+852 6114 9265| stefania.alborghe...@datastax.com [image: cassandrasummit.org/Email_Signature] <http://cassandrasummit.org/Email_Signature>
