Stream: shorthand
Topic: SUSHI Versioning Approach
Chris Moesel (Apr 26 2021 at 19:45):
We are at a point where we need to make some decisions regarding versioning. The basic question is:
- Should SUSHI follow semantic versioning (increasing the major version number whenever there are breaking changes)?
- Or should SUSHI align its version numbers with FHIR Shorthand version numbers (increasing the major version number only when FSH increases its version number)?
We've seen examples of both approaches, and while some of us on the team have strong opinions on this, we would like to know what would be least confusing (and most helpful) to the community.
Christian Nau (Apr 27 2021 at 09:49):
I'm personally a big fan of semantic versioning. This way it is clear to me when breaking changes will happen without the need of looking through release notes.
An alignment with FHIR Shorthand version numbers might seem a nice idea, but in my opinion the version number of tooling should not depend on version-numbers of other systems. (Although it is very helpful that you include the supported Shorthand version number in the version info of sushi!)
sushi -v
SUSHI v1.3.2 (implements FHIR Shorthand specification v1.1.0)
Patrick Werner (Apr 27 2021 at 20:10):
:+1: for semver
Last updated: Apr 12 2022 at 19:14 UTC
