Version scheme understanding

[sshedi]

Hi @kgold2 @kgoldman

Hope your are doing well, can you please give more info on the new versioning scheme followed?
https://github.com/kgoldman/ibmswtpm2/releases/tag/rev183-2024-08-02

Till 1682, this was the naming scheme - https://github.com/kgoldman/ibmswtpm2/releases/tag/rev1682
And it changed fully now, is rev183-2024-08-02 a ready to use release or beta sort of release?

Is it possible to continue with older naming scheme for release? Please assist.

[kgoldman]

That old numbering scheme came from svn tags. (git wasn't invented when these projects started). I'm now following the TCG spec revision. TCG recently changed the numbering, so the numbers will only increment when TCG publishes a spec. Thus, I added a date to indicate bug fixes or errata.

[sshedi]

Hi @kgoldman thanks for the response. If I understand correctly, I can assume this is going to be the version scheme that will get used going forward and will not go back the earlier way, right?

[kgoldman]

The rev will follow the TCG TPM library specification. If you have any suggestion for how to handle official TCG errata (not implementation bugs), let me know.

[sshedi]

Does this work? rev183-2024-08-02 -> 20240802.183 for tag names? This makes it easy to ship this as a deb or rpm package, this way version only grows higher, easy to understand and maintain. Do you see any issues in this approach? Again, thanks a lot for your response.

[kgoldman]

I think it will only grow either way. Both the revision and the date only increase. My thought was that the revision (183) is more significant than a patch - like semantic versioning - major.minor.patch - most significant first.

Errata is a third field, once TCG starts issuing errata that affect operation.

[sshedi]

That is also fine but it should be an upward growing scheme, helps a lot while shipping this package as rpm.

rev183-2024-08-02 -> 183.20240802

Is fine too, but please finalise on something and let me know what convention you will follow going forward, we will use the same in rpm specs.