You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cassandra.apache.org by Josh McKenzie <jm...@apache.org> on 2016/01/04 23:54:22 UTC
New branches for 3.2 & 3.3, current merge path
As part of the new tick-tock release cycle, we're experimenting with a
week-long code-freeze before voting in order to do more thorough
pre-release testing of candidates. I've created 2 new branches for commits:
*cassandra-3.2*: frozen as of 01d26dd3fc35a6b22a538f75545b0d9b739ee48d. We
plan on committing two more tickets to this branch before release
(currently targeting 1/8/16 for vote):
1. https://issues.apache.org/jira/browse/CASSANDRA-6696
2. https://issues.apache.org/jira/browse/CASSANDRA-9303
*cassandra-3.3*: for stabilization patches only, to be released in Feb '16
*Merge path is now:*
* stabilization*: [cassandra-2.2 -> cassandra-3.0 ->] cassandra-3.3 ->
trunk
* new features / improvements*: trunk (3.4)
*Note:*
cassandra-3.2 is not on the merge path and we're only targeting the
above 2 tickets for that branch.
cassandra-2.1 is now critical bug-fixes only and is no longer in the
merge path.
Thanks.
~Josh