Gang, I am proposing that we start use a variant of the "Linux Standard" on versioning.
Format: MAJOR.MINOR.MICRO MAJOR=Incompatible changes either at source or binary level. MINOR=Feature enhancements, both source and binary compatible with earlier versions in the same MAJOR line. MICRO=New build. Furthermore; ODD MINOR = development in progress. EVEN MINOR = released versions. Example of the net effect; We are currently working on Merlin 3.3, and should frequently create dev versions and upload them to repository, 3.3.1, 3.3.2 . . . 3.3.29. Perhaps as often as a few times a week or so. Automated? Each version is tagged in the CVS. Part of the dev-release is that the version MICRO is increased in the source. At some point, a vote for release is made by PMC to make a release. Whatever dev version that is voted upon becomes the 3.4.0 release, and the CVS HEAD is moved to 3.5.0. Once 3.4.0 is out, only bug fixes are patched in that line, and the aggressive development continue in the 3.5.0. Another net effect is the abandoning of SNAPSHOT. It is not working for me to use it. Creates more confusion than helps in the daily work. WDYAT? Niclas -- +---------//-------------------+ | http://www.bali.ac | | http://niclas.hedhman.org | +------//----------------------+ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
