I really wouldn't go by the tick tock blog post, considering tick tock is dead.
I'm still not wild about putting any 3.0 or 3.x into production. 3.0 removed off heap memtables and there have been enough bugs in the storage engine that I'm still wary. My hope is to see 3.11.x get enough bug fixes to where most people just skip 3.0 altogether. I'm not sure if we're there yet though. On Wed, May 31, 2017 at 9:43 AM Junaid Nasir <jna...@an10.io> wrote: > as mentioned here > http://www.datastax.com/dev/blog/cassandra-2-2-3-0-and-beyond > >> Under normal conditions, we will NOT release 3.x.y stability releases for >> x > 0. That is, we will have a traditional 3.0.y stability series, but the >> odd-numbered bugfix-only releases will fill that role for the tick-tock >> series — recognizing that occasionally we will need to be flexible enough >> to release an emergency fix in the case of a critical bug or security >> vulnerability. >> We do recognize that it will take some time for tick-tock releases to >> deliver production-level stability, which is why we will continue to >> deliver 2.2.y and 3.0.y bugfix releases. (But if we do demonstrate that >> tick-tock can deliver the stability we want, there will be no need for a >> 4.0.y bugfix series, only 4.x tick-tock.) > > > On Wed, May 31, 2017 at 9:02 PM, pabbireddy avinash < > pabbireddyavin...@gmail.com> wrote: > >> Hi, >> >> We are planning to deploy a cassandra production cluster on 3.X /3.0.X . >> Please let us know if there is any stable version in 3.X/3.0.X that we >> could deploy in production . >> >> Regards, >> Avinash. >> > >
