Re: On release numbering

[John Stoffel]

>>>>> "Ulrich" == Ulrich Mueller <ulm@gentoo.org> writes:

>>>>> On Sat, 13 Jul 2024, John Stoffel wrote:
>>> gitlab main should have a version number of 8.3.x.

>> Awesome.   I'd suggest you/we append the latest git tag/commit number
>> into the version string. then it's *really* clear what's happening.  

> Does "commit number" mean the commit ID (a string of hexadecimal chars),
> or the number of commits since the last release tag (that e.g. occurs in
> the output of "git describe")?

The second, the output of the 'git describe'  And this would only be
used for development builds so that we can keep track of what people
are running.  

For releases, I think we need to just move to 8.3.0 and start there.  

> If you mean the former, then it may not be possible to use it in
> distro packages (because hexadecimal may not be allowed in version
> numbers).  Also, commit IDs don't monotonically increase, which
> makes it impossible to check if the package needs to be updated on a
> user's system.

Yes, I realize that.  But when we're testing stuff, like I am now with
the latest bleeding edge (and I need to file some reports) it would
help to have an easy to report number that we can track down.