//////////////////////////////////////////////////////// This file explains the branches naming scheme and also the general release policies of the MlView project. ///////////////////////////////////////////////////////// Initial author: Dodji Seketeli <dodji@seketeli.org> Last Modification date: December 27, 2002 I) Current release Policy ///////////////////////// Then, the development will be done following to branches: STABLE and UNSTABLE. STABLE: stable releases will be those identified as being "useable". By useable I mean, releases that "don't crash too much." Stable releases have even minor version number. (ex: 0.2.1 or 1.4.3 or 3.0.1) UNSTABLE: unstable release are "unstable" by definition. They are there to prepare stable releases. Once a serie of unstable releases has been seriously debugged and becomes "useable", it can be renamed into a stable release. Unstable releases have odd version number. (ex 0.3.2 or 1.5.4 or 3.1.2) II) Previous Release policy /////////////////////////// We consider three types of releases: *stable releases *release candidates *development snapshot Stable Releases --------------- Stable releases are releases that users can use on a daily basis. There are considered as stable. If users experience too much crashes using stable releases, that means that we failed in our release process. Stable releases have a release number made of dots and numbers. example: 0.0.2 Release Candidates ------------------ Release candidates are releases that prepare stable releases. There are there to say "Hey this a first attempts toward the stable release, please, use it and tell us what you think about it". Release candidates may be unstable or have some buggy behaviours. Release candidates have a release number made of numbers, dots and the letters 'rc'. example: 0.0.2-rc2 means "the second release candidate towards the 0.0.2 stable release." Note that the 'rc' is separated from the "0.0.2" by a dash, not an underscore. Development snapshot -------------------- Development snapshot are releases mainly made for other other programmers to test hot features and to add knew ones. There are useally available as tarball only. Development snapshot have release number made as in the example: example: devel-0-0-2-2002W15D16 where 'devel-0-0-2' is the name of the branch in which the snapshot has been made, and '2002W15D16' is the date of the snapshot. '2002W15D2' means "Year 2002, Week 15, Day 2 (Tuesday) .
