Is there consensus on a way forward with this? Is there going to be a three branch plan with “features”, “testing”, and “stable” starting with 4.0? Or is this still in the discussion mode? External to this thread there have been decisions made to create third party LTS releases and hopes that the project would decide to address the concerns in this thread. It seems like this is the place to complete the discussion.
> On Sep 26, 2016, at 10:52 AM, Jonathan Haddad <j...@jonhaddad.com> wrote: > > Not yet. I hadn't seen any Jirsa before to release a specific version, only > discussion on the ML. > > I'll put up a Jira with my patch that back ports the bug fix. > On Mon, Sep 26, 2016 at 8:26 AM Michael Shuler <mich...@pbandjelly.org> > wrote: > >> Jon, is there a JIRA ticket for this request? I appreciate everyone's >> input, and I think this is a fine proposal. >> >> -- >> Kind regards, >> Michael >> >> On 09/14/2016 08:30 PM, Jonathan Haddad wrote: >>> Unfortunately CASSANDRA-11618 was fixed in 3.6 but was not back ported to >>> 3.5 as well, and it makes Cassandra effectively unusable if someone is >>> using any of the 4 types affected in any of their schema. >>> >>> I have cherry picked & merged the patch back to here and will put it in a >>> JIRA as well tonight, I just wanted to get the ball rolling asap on this. >>> >>> >> https://github.com/rustyrazorblade/cassandra/tree/fix_commitlog_exception >>> >>> Jon >>> >> >>
