Version bump.

[Dan Poirot]

...answers a lot of questions before they are even asked!

Compiling the git SHA string into the code (-v) is huge too. 

I use that in my code and find it reliable and highly useful.

- dan


-----Original Message-----
From: devel [mailto:devel-bounces at ntpsec.org] On Behalf Of Hal Murray
Sent: Wednesday, March 30, 2016 3:42 AM
To: devel at ntpsec.org
Subject: Re: Version bump.


dtpoirot at gmail.com said:
> Folks also use odd numbers for development branches and adding a dot 
> release for new features.

I think we should seriously consider the odd-even aproach.  That solves most
of the ambiguity problem.  It uses the bottom bit of a numeric slot to
indicate firm vs fuzzy status rather than our schemes for adding a "+" or
"-" 
to the version string.

waf calls our version string MAJOR.MINOR.REV

I think we would use odd/even in two places, one for MINOR and again for
REV. 
 git tags would only have even numbers in both slots.  We would bump the REV
slot on an old release if we go back and patch it.

--
These are my opinions.  I hate spam.



_______________________________________________
devel mailing list
devel at ntpsec.org
http://lists.ntpsec.org/mailman/listinfo/devel