Release cycle

From Freeplane - free mind mapping and knowledge management software
Revision as of 17:49, 5 March 2010 by Ewl (talk | contribs) (Created page with '= Release Cycle = File:Freeplane Release model.png As shown above, the release cycle of Freeplane consists of 4 phases: ; Alpha : 3 months of "wild" development on MAIN/HEA...')
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Release Cycle

Freeplane Release model.png

As shown above, the release cycle of Freeplane consists of 4 phases:

Alpha 
3 months of "wild" development on MAIN/HEAD/trunk (CVS resp. SVN talk)

⇒ Branch the next release e.g. Branch_1.0.x - developers can continue to bring in new features on MAIN/HEAD/trunk.

Beta 
2 months of bug fixing releases on Branch_1.0.x - that would be Beta releases.

⇒ Create RC1 (Release Candidate) - call for translations, 3rd party plugins and packaging.

Release Candidate (RC) 
1 month of integration of translations + critical bug fixing (3rd party plugins and packaging as well, but final packaging can only happen after final release so we can only make sure that it all happen in a limited timeframe).

⇒ Create Final release, e.g. 1.1.0.

Stable 
new bug fixing / stable releases can be done as required, called 1.1.1, 1.1.2...

⇒ Restart the cycle e.g. for 1.2.x