[...]
Hello
Can we please stick with a versioning/file-name scheme?
Releases are named "2017.0" or "2018.0" in the announcements
but report themselves to be 2017.0.0 and 2018.0.0 respectively while
the filename has the third component or not (hugin-2018.0.0.tar.bz2
vs hugin-2017.0.tar.bz2). Beta/rc are using four different schemes:
hugin-2019.0beta2.tar.bz2
hugin-2019.0.beta1.tar.bz2
hugin-2016.2.0-rc2.tar.bz2
hugin-2014.0.0_rc2.tar.bz2
This is unnecessary painful if you want to use something like Debian's
uscan to automatically grab the latest release (and report its
existence).
I would suggest the following:
* Announce the complete version and use it as filename component
(Hugin 2019.0.0 released --> hugin-2018.0.0.0.tar.bz2)
* For Beta/rc versions, still use the complete version number in both
announcement and filename. In the filename separate the "beta1" from
the regular version, and use a character that cannot appear in a
regular release number for separation (not dot), e.g:
hugin-2019.0.0_beta2.tar.bz2 or hugin-2019.0.0+beta2.tar.bz2 or
hugin-2019.0.0~beta2.tar.bz2. I would prefer the ~. Choose one and
stick with it.
Thanks in advance, cu Andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'