pick a versioning scheme

bluesky / libhkl

Build the hkl library for hklpy

https://people.debian.org/~picca/hkl/hkl.html

GNU General Public License v3.0

0 stars 0 forks source link

pick a versioning scheme #5

Closed prjemian closed 11 months ago

prjemian commented 11 months ago

What versioning scheme should this repo use? Seems we have a choice. Upvote whichever comment below.

prjemian commented 11 months ago

semver starting from 1.0.0

Clear identification of a new libhkl release.
Need to examine release notes to find a specific version.

prjemian commented 11 months ago

Same versioning as hkl repo

Easy to correlate release of libhkl with hkl repo version.
Verbose if/when changes are need to a released version of libhkl

prjemian commented 11 months ago

@mrakitin @klauer Thoughts? Votes?

klauer commented 11 months ago

It might be easier to just follow semver and decouple from the upstream (which is far from semver as far as I can tell).

That said, we are just packaging/building that library so it sorta makes sense to follow their versioning. So I'm a bit split and both get a 👍 from my indecisive self.

prjemian commented 11 months ago

FWIW: the conda-forge recipe builds with the 2173 release

prjemian commented 11 months ago

Progress noted, I will plough ahead with semver (since, if we change our minds and track hkl versioning scheme, that is still in the sequence of semver, in that v1.0.0 < v5.0.0.3375). If we switch to hkl's versioning, we cannot go back to semver.

prjemian commented 11 months ago

Which means I will delete the https://github.com/bluesky/libhkl/releases/tag/v5.0.0.2173rc1 tag.

prjemian commented 11 months ago

semver it is.