[xiphos-devel] getting a new release out

Caleb Maclennan caleb at alerque.com
Sun Apr 26 00:33:00 MST 2020

On Sat, Apr 25, 2020 at 11:50 PM Karl Kleinpaste <karl at kleinpaste.org> wrote:
> - I need to understand how the version stamp thing happens, now that Caleb's source_version.txt is in play. We simply tag just prior to doing github release?

Yes, just simply tag, then build. There should be virtually nothing to do.

In fact it's kind of important you don't do anything else. If you tag
a commit as, say, "v4.2.0", then realize you forgot something and
commit a small change, then build, what you build won't be v4.2.0 at
all it will be v4.2.0.1. In other words to get the actual release
version as tagged you _must_ build from the actual tagged commit. You
can't fudge and actually build something else and just call it
something its not.

By the way I would be inclined to make the next release v4.2.0 not
v4.1.1. If you actually follow SemVer there are a lot more changes
than should fit in only a patch version bump. As a distro packager I
expect patch versions to build and install virtually identically to
previous versions. This release will require an entirely new set of
build commands, and even the dependencies have changed. Even if there
is not a much in the way of user facing changes the under-the-hood
stuff is radically different and shouldn't be hidden behind a patch
release number bump — at least not in my opinion as a downstream

More information about the xiphos-devel mailing list