With the move to git, the packaging version scheme had to change due to git
not having any monotonic revision number. Before, the builder was using svn
for everything, even git thanks to Github's svn bridge. Now, git is used
where applicable.
So in our repos, the version scheme for git sources has changed thusly:
Old: 3.5.0~r84259
New: 3.5.0+g610~e82a45ac
The old was version followed by ~r and the svn revision number. New is
version followed by +g and a number from 'git rev-list --count
--first-parent' followed by ~ and 8 digits of the commit hash.
The version scheme for svn sources has also changed from ~r to +s,
so 1.1.2~r12661 is now 1.1.2+s12661.
The change from ~ to + has been on the wishlist for a long time, because in
Debian terms ~ is always strictly less than and this caused some annoyances
where 3.5.0 was seen as greater than 3.5.0~r83421, so our own packages
would not always be seen as newer than mainline.
In mainline Debian/Ubuntu, going forward we'll discard all the suffixes and
just use 3.5.0.
Which is where how you do releases will be important. A release should be
tagged in git with prefix v, so 3.5.0 should be released under tag v3.5.0.
I've seen some releases marked without the prefix v, which we can't really
use.
Please follow https://semver.org/ without suffixes, and remember to adjust
the version in configure.ac before tagging a release. I don't care about
Makefile.am - the version in there is not used by anything and should
really just be removed. Only the version in configure.ac matters.
If you don't adjust the version and then continue working after tagging a
release, correcting the version and tag becomes an annoying mess of
branches.
If git is too alien, Github has a nice UI for release tagging. Just
remember the v.
Also, just like I had a mirror of the whole svn repo, I'm keeping mirrors
of the git repos at https://apertium.projectjj.com/git/ - they'll be
mirrored over as they are built, and then kept up to date by the builder.
-- Tino Didriksen
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Apertium-stuff mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/apertium-stuff