Re: cassandra-3.1 branch and new merge order

2015-11-10 Thread Aleksey Yeschenko
3.0.1 and 3.1 will be identical this time around - that’s just a consequence of the transition. Starting with 3.0.2 and 3.2, however, the branches will diverge. Skipping one or the other would look weird and break continuity, so we are still going to release both, despite them containing the sam

Re: cassandra-3.1 branch and new merge order

2015-11-10 Thread Björn Hegerfors
So there is no reason for an end-user to actually use 3.1, because it will have the same features as 3.0.x, but won't be maintained? 3.0.x for high x will be 3.1 plus more bug fixes. I'm not saying that's bad. Starting from 3.2, using any subsequent version will make sense. On Tue, Nov 10, 2015 at

Re: cassandra-3.1 branch and new merge order

2015-11-10 Thread Paulo Motta
3.0.x is an interim branch during the transition to the new tick tock release model, which will receive backported patches from bug-fix releases (3.1, 3.3, etc) that affect 3.0, so no new features will go into 3.0.x. So users can safely go to 3.0 before adopting tick tock, knowing they will be serv