Folks also use odd numbers for development branches and adding a dot release for new features.
Even numbers are for release branches with dot releases for maintenance release. Increment in the version number would indicate a major milestone. The '-v' command line switch should report the short version of the git SHA for traceability. Much easier to follow the story this way... > On Mar 25, 2016, at 12:22 PM, Eric S. Raymond <e...@thyrsus.com> wrote: > > Amar Takhar <v...@darkbeer.org>: >>> On 2016-03-25 09:47 -0400, Eric S. Raymond wrote: >>> Amar Takhar <v...@darkbeer.org>: >>>> Advancing the version stops that confusion. >>> >>> Another praxtice often used is to append "+" to the version after a release. >> >> Oh? I've never heard of that interesting. I will throw that in it can't >> hurt. >> I'm going to throw a release tarball up of 0.9.2 on the FTP today. >> >> So, ntpd 0.9.2-afceec0+ >> >> ? > > If you're going to use the "+" convention a git hash is not normally also > used. > > The tarball would be "0.9.2". Then the version string would be bumped to > "0.9.2+" > to mark that commits are open again. The next release tarball would be > "0.9.3", > and so forth. > -- > <a href="http://www.catb.org/~esr/";>Eric S. Raymond</a> > _______________________________________________ > devel mailing list > devel@ntpsec.org > http://lists.ntpsec.org/mailman/listinfo/devel _______________________________________________ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
