Normally, since 3.5 just came out, it would be wise to see if people report any problems over the next few weeks.
But... the new tick-tock release process is designed to assure that these odd-numbered releases are only incremental bug fixes from the last even-numbered feature release, which was 3.4. So, 3.5 should be reasonably stable. That said, a bug-fix release of 3.0 is probably going to be more stable than a bug fix release of a more recent feature release (3.4). Usually it comes down to whether you need any of the new features or improvements in 3.x, or whether you might want to keep your chosen release in production for longer than the older 3.0 releases will be in production. Ultimately, this is a personality test: Are you adventuresome or conservative? To be clear, with the new tick-tock release scheme, 3.5 is designed to be a stable release. -- Jack Krupansky On Thu, Apr 14, 2016 at 3:23 PM, Jean Tremblay < jean.tremb...@zen-innovations.com> wrote: > Hi, > Could someone give his opinion on this? > What should be considered more stable, Cassandra 3.0.5 or Cassandra 3.5? > > Thank you > Jean > > > On 12 Apr,2016, at 07:00, Jean Tremblay < > jean.tremb...@zen-innovations.com> wrote: > > > > Hi, > > Which version of Cassandra should considered most stable in the version > 3? > > I see two main branch: the branch with the version 3.0.* and the > tick-tock one 3.*.*. > > So basically my question is: which one is most stable, version 3.0.5 or > version 3.3? > > I know odd versions in tick-took are bug fix. > > Thanks > > Jean >
