Page History

...

• Release branches will be created approximately once per year. We have decided recently (February 2009) to use the same release numbering scheme than Ubuntu (for instance, 9.3 4 means released in 2009 .Marchin April). This information is used in backend footer to know wich Release.revision is used...
• The trunk will never go into a feature-freeze state but rather development will continue and contributions will be accepted both immediately before and after the cutoff revision for a release branch
• An initial pre-built package will be created and made available to help get people started with the branch
• Once a release branch stabilizes an initial "stable" release tag and pre-built package will be issued
• Patches on the release branch can be created and applied whenever users desire
• Follow on release tags and pre-built packages will be issued when major problems are discovered and fixed, and periodically to represent a significant number of fixes and updates
• Each new release tag and pre-built package will be represented by a third position version number change (since February 2009 seems that we will prefer to use the revision number for that)
• Because it needs too much work, at some point older releases will not be supported by the community (trunk patches not backported)

...