On 13:50 Mon 22 Sep , Aurélien Bouteiller wrote: > Could also start at 1.9.1 instead of 1.9.0. That gives a free number > for the “trunk” nightly builds.
Could also start at 2.1 instead of 2.0. That gives a free boost in maturity. More seriously, I'd suggest to use Semantic Versioning[1], which is actually straight forward for both, developers and users. I'm quoting the linked website: > Given a version number MAJOR.MINOR.PATCH, increment the: > > 1. MAJOR version when you make incompatible API changes, > 2. MINOR version when you add functionality in a backwards-compatible > manner, and > 3. PATCH version when you make backwards-compatible bug fixes. > > Additional labels for pre-release and build metadata are available as > extensions to the MAJOR.MINOR.PATCH format. [1] http://semver.org/ HTH -Andreas -- ========================================================== Andreas Schäfer HPC and Grid Computing Chair of Computer Science 3 Friedrich-Alexander-Universität Erlangen-Nürnberg, Germany +49 9131 85-27910 PGP/GPG key via keyserver http://www.libgeodecomp.org ========================================================== (\___/) (+'.'+) (")_(") This is Bunny. Copy and paste Bunny into your signature to help him gain world domination!
signature.asc
Description: Digital signature
