Re: Problems with gnits standard and git-version-gen

2014-02-08 Thread Nate Bargmann
Some advice I received from a Debian developer (packager) was that it works better when upstream projects refrain from using the hyphen '-' in their version string. The packaging software will consider 1.0-rc1 to be more recent than 1.0 as the packaging system appends '-*' to the end of the

Re: Problems with gnits standard and git-version-gen

2014-02-07 Thread Karl Berry
1.00rc0 Personally, when I see a version number like that, I'm never sure what it means. Probably the first rc leading up to 1.00, but maybe it is an rc for 1.01 after 1.00. And suffixes sort badly in long lists (see, e.g., http://ftp.isc.org/isc/bind9/). Anyway. Not trying to change your

Re: Problems with gnits standard and git-version-gen

2014-02-07 Thread Harlan Stenn
For NTP, we have a kinda hard to describe but easy to read mechanism. For development versions (odd-number minor releases) each new issue gets a bumped point number (major.minor.point). If that issue is a release candidate it gets a -RC suffix. For stable versions (even-number minor releases)

Re: Problems with gnits standard and git-version-gen

2014-02-07 Thread Werner LEMBERG
1.00rc0 Personally, when I see a version number like that, I'm never sure what it means. Probably the first rc leading up to 1.00, but maybe it is an rc for 1.01 after 1.00. Well, I have *never* encountered that `1.00rc0' means a release candidate for 1.01. Have you? And suffixes

Problems with gnits standard and git-version-gen

2014-02-06 Thread Werner LEMBERG
Folks, I try to make a release candidate. Theoretically, I could use version `0.99.99' or something similar, however, it looks much nicer IMHO to use `1.00rc0'. Unfortunately, the gnits standard currently prevents this. To be more precise, it's the following regex in the automake script: