Re: [RELEASE] Apache Cassandra 3.1 released

> There's not going to be a 3.3.x series, there will be one 3.3 release (unless > there is a critical bug, as mentioned above). > > There are two separate release lines going on: > > 3.0.1 -> 3.0.2 -> 3.0.3 -> 3.0.4 -> ... (every release is a bugfix) > > 3.1 -> 3.2 -> 3.3 -> 3.4 -> ... (odd

Re: [RELEASE] Apache Cassandra 3.1 released

On Fri, Dec 11, 2015 at 1:59 AM, Janne Jalkanen wrote: > > So there is no reason why you would ever want to run 3.1 then? > Probably not. > Why was it released? > For consistency. It's the first release in the new tick-tock release scheme. Skipping that would

Re: [RELEASE] Apache Cassandra 3.1 released

Thanks for this clarification, however... > So, for the 3.x line: > If you absolutely must have the most stable version of C* and don't care at > all about the new features introduced in even versions of 3.x, you want the > 3.0.N release. So there is no reason why you would ever want to run

Re: [RELEASE] Apache Cassandra 3.1 released

Josh, Thank you very much for the clarification. On Thu, Dec 10, 2015 at 11:13 AM, Josh McKenzie wrote: > Kai, > > >> The most stable version will be 3.1 because it includes the critical >> fixes in 3.0.1 and some additional bug fixes > > 3.0.1 and 3.1 are identical. This

Re: [RELEASE] Apache Cassandra 3.1 released

Thanks, Josh and Paulo--that's much clearer. ​

Re: [RELEASE] Apache Cassandra 3.1 released

> Will 3.2 contain the bugfixes that are in 3.0.2 as well? If the bugfix affects both 3.2 and 3.0.2, yes. Otherwise it will only go in the affected version. > Is 3.x.y just 3.0.x plus new stuff? Where most of the time y is 0, unless there's a really serious issue that needs fixing? You can't

Re: [RELEASE] Apache Cassandra 3.1 released

Paulo, Thank you for the examples. So if I go to download page and see 3.0.1, 3.1 and 3.2. The most stable version will be 3.1 because it includes the critical fixes in 3.0.1 and some additional bug fixes while doesn't have any new features introduced in 3.2. In that sense 3.0.1 becomes obsolete

Re: [RELEASE] Apache Cassandra 3.1 released

Kai, > The most stable version will be 3.1 because it includes the critical fixes > in 3.0.1 and some additional bug fixes 3.0.1 and 3.1 are identical. This is a unique overlap specific to 3.0.1 and 3.1. To summarize, the most stable version should be x.Max(2n+1).z. Going forward, you can

Re: [RELEASE] Apache Cassandra 3.1 released

I’m sorry, I don’t understand the new release scheme at all. Both of these are bug fixes on 3.0? What’s the actual difference? If I just want to run the most stable 3.0, should I run 3.0.1 or 3.1? Will 3.0 gain new features which will not go into 3.1, because that’s a bug fix release on 3.0?

Re: [RELEASE] Apache Cassandra 3.1 released

Janne, You are not alone. I am also confused by that "Under normal conditions ..." statement. I can really use some examples such as: 3.0.0 = ? 3.0.1 = ? 3.1.0 = ? 3.1.1 = ? (this should not happen under normal conditions because the fix should be in 3.3.0 - the next bug fix release?) On Wed,

Re: [RELEASE] Apache Cassandra 3.1 released

Hi, I feel the same as well. Would you skip 3.2 when you release another round of bug fixes after one round of bug fixes? Or would 3.2 be released after 3.3.? :P BR, Hannu > On 09 Dec 2015, at 16:05, Kai Wang wrote: > > Janne, > > You are not alone. I am also confused by

Re: [RELEASE] Apache Cassandra 3.1 released

I'm still confused, even after reading the blog post twice (and reading the linked Intel post). I understand what you are doing conceptually, but I'm having a hard time mapping that to actual planned release numbers. > The 3.0.2 will only contain bugfixes, while 3.2 will introduce new features.

Re: [RELEASE] Apache Cassandra 3.1 released

This explains the new release plans in detail: http://www.planetcassandra.org/blog/cassandra-2-2-3-0-and-beyond/ 3.0.1 and 3.1 are a special case, because they happen to be identical. However, 3.0.2 will not be the same as 3.2. The 3.0.2 will only contain bugfixes, while 3.2 will introduce new

[RELEASE] Apache Cassandra 3.1 released

The Cassandra team is pleased to announce the release of Apache Cassandra version 3.1. This is the first release from our new Tick-Tock release process[4]. It contains only bugfixes on the 3.0 release. Apache Cassandra is a fully distributed database. It is the right choice when you need