[펌] 카산드라는 매달 출시 계획을 갖는다.

카산드라는 3.0부터는 매달 출시할 계획이라고 한다.  짝수 달은 버그 픽스를 포함하고 홀수 달은 버그만 하는 정책을 따른다고 한다. 인텔의 틱톡 모델(예전 아저씨들이 플랫폼 릴리즈를 할처럼 돌아갔다)처럼 간다고 한다. 

http://www.datastax.com/dev/blog/cassandra-2-2-3-0-and-beyond

After 3.0, we’ll take this even further: we will release 3.x versions monthly.  Even releases will include both bugfixes and new features; odd releases will be bugfix-only.  You may have heard this referred to as “tick-tock” releases, after Intel’s policy of changing process and architecture independently.

The primary goal is to improve release quality.  Our current major “dot zero” releases require another five or six months to make them stable enough for production.  This is directly related to how we pile features in for 9 to 12 months and release all at once.  The interactions between the new features are complex and not always obvious.  2.1 was no exception, despite DataStax hiring a full time test engineering team specifically for Apache Cassandra.

We need to try something different.  Tick-tock releases will dramatically reduce the number of features in each version, which will necessarily improve our ability to quickly track down any regressions.  And “pausing” every other month to focus on bug fixes will help ensure that we don’t accumulate issues faster than we can fix them.

http://www.intel.com/content/www/us/en/silicon-innovations/intel-tick-tock-model-general.html