On Thu, 2009-04-02 at 13:01 +0200, Dr. Stephen Henson wrote: <snip> > Under this scheme.... > > 1. Bug fix releases will change the letter. > E.g. 1.0.0 -> 1.0.0a > > 2. Feature releases will change the last (minor) number. > E.g. 1.0.0 -> 1.0.1 > > 3. Major development will change the second (major) number. > E.g. 1.0.0 -> 1.1.0
<random thoughts> How do you call the first number then, or what must happen to change it? Compared to other packages, an usual versioning scheme is: "packagename-major.minor.micro": changing micro for bugfixes. changing minor for added features. changing major for major development. So far it's identical to what you do, except that they omit what you have as first number. And they do 'micro' versioning with numbers too. When using letters, how would you call the 27th bugfix release? Even if I can live with, I just don't really like the letter. If you need to have 'major' as the _second_ number, then I prefer having 'micro' as the fourth number. </random thoughts> Just my 0.02, don't want to force anything... /haubi/ ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [email protected] Automated List Manager [email protected]
