On Wed, Mar 14, 2018 at 2:26 AM, Tino Didriksen <tino.didrik...@gmail.com> wrote: > 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.
I'll add: GitHub allows uploading files associated with tagged releases. Please be sure to always generate a tarball with "make dist" and upload it to GitHub after you've tagged it. Although GitHub does provide automatically generated .tar.gz and .zip archives for tags, they're unsuitable for a number of reasons: - They don't include pregenerated configure scripts, meaning the end user or packager must run Autoconf and Automake manually. - They don't have stable checksums, making them problematic for packaging: the files can vary depending on the versions of tar, zip, gzip, etc. running on GitHub's backend, and have varied this way in the past. - They don't contain Git submodules or any metadata associated with them. So please remember to always generate a proper distribution tarball and upload it to the releases page once you've pushed the tag. -- Anthony J. Bentley ------------------------------------------------------------------------------ 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 Apertium-stuff@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/apertium-stuff
