A new release cycle
For the Blender 2.6x series, we will use this new release cycle, to release more frequently and predictable for users and developers.
A release cycle is 8-12 weeks long. The duration of the cycle will be set in Bcon1.
|Bcon1: Set targets||2-3 weeks||Confirm targets, make release schedule, start merging approved work to trunk|
|Bcon2: Merge/Stabilize||3-4 weeks||Remaining branches can be merged in, but only the ones agreed on in Bcon1.
Module work can continue, focus is on stabilizing and fixing.
|Bcon3: Fixing only||1-2 weeks||go/nogo on branches. If a branch added in Bcon1/2 is still very unstable it will be reverted. Focus is on bugfixing.|
|Bcon4: Release candidate||1 week||Release candidate is made, only critical fixes are allowed|
|Bcon5: Release & Freeze||1-2 days||SVN is frozen. Splash & version commit, Release Ahoy and clear call for freeze/unfreeze.|
(Test) Build Schedule
|First Testbuild||Beginning of Bcon3||All new features are added, user can test. At this point documentation efforts can also start.|
|Release Candidate||Beginning of Bcon4||The release candidate to make sure, no critical bugs remain.|
|Final||Middle of Bcon5||Final stable release|