Update to Hector 2.1 about pyhector HOT 12 CLOSED

I'd propose a versioniong scheme to track Hector's main version and add a letter to add further versions for Pyhector, e.g.

2.1.a - First Pyhector version for Hector 2.1
2.1.b - Second Pyhector version for Hector 2.1 (e.g. a bugfix)

Our userbase is so small that i don't see a need to differentiate between major/minor breaking changes.

from pyhector.

I like that! It implies we only have new pyhector releases on new hector minor version changes? Or just continue our bugfix letter with a new hector bugfix version? @rgieseke Could you include that in the docs, please?

from pyhector.

Hector actually uses semver (or some variant):

https://github.com/JGCRI/hector/releases

So that would be
2.1.1.a -- first Pyhector version of Hector 2.1.1
2.1.1.b -- Bugfix of Pyhector
2.1.1.c -- New feature in Pyhector API
2.1.2.a -- First Pyhector version of Hector 2.1.2
2.1.2.b -- Change Pyhector API

Or we could only add a letter if we actually change something ...
2.1.3 -- First Pyhector release of Hector 2.1.3
2.1.3.a -- Bugfix in Pyhector

It could very likely that we don't have to do any (or very few) changes in Pyhector.

from pyhector.

2.1.0 has been tagged:

https://github.com/JGCRI/hector/releases/tag/v2.1.0

(No changelog though.)

from pyhector.

We could also skip the last dot:

2.1.1
2.1.1a
2.1.1b
2.2.0
2.2.0a

from pyhector.

Or:

2.1.1
2.1.1-a
2.1.1-b
2.2.0
2.2.0-a

from pyhector.

voting for 2.1.1b

from pyhector.

Since 2.1.1a 2.1.1b gets read as "alpha" or "beta", maybe we should use

Local version identifiers

Local version identifiers MUST comply with the following scheme:

[+]

They consist of a normal public version identifier (as defined in the previous section), along with an arbitrary "local version label", separated from the public version identifier by a plus. Local version labels have no specific semantics assigned, but some syntactic restrictions are imposed.

Local version identifiers are used to denote fully API (and, if applicable, ABI) compatible patched versions of upstream projects. For example, these may be created by application developers and system integrators by applying specific backported bug fixes when upgrading to a new upstream release would be too disruptive to the application or other integrated system (such as a Linux distribution).

E.g. something like
2.1.0+pyhector.1

from pyhector.

Maybe not :-)

Local version identifiers SHOULD NOT be used when publishing upstream projects to a public index server, but MAY be used to identify private builds created directly from the project source. Local version identifiers SHOULD be used by downstream projects when releasing a version that is API compatible with the version of the upstream project identified by the public version identifier, but contains additional changes (such as bug fixes). As the Python Package Index is intended solely for indexing and hosting upstream projects, it MUST NOT allow the use of local version identifiers.

from pyhector.

nice. but maybe the other way around: 2.1.4+hector2.1.0

from pyhector.

I think PyPI would complain. Still trying to find a tool which uses 1.2.3.4

from pyhector.

While any number of additional components after the first are permitted under this scheme, the most common variants are to use two components ("major.minor") or three components ("major.minor.micro").

from pyhector.