I’d like to cut a new release in March. And so we confront one of the many ambiguities in semantic versioning. I believe all changes qualify for a patch release (2.46.2) except maybe the work by @graphgalaxy that makes the JSON output ordered (thanks again!). Should we be considering this a patch release or a minor version bump (2.47.0)?
1 Like
I’m not aware of any ambiguities in semver. At least not in this case. If there is new functionality added in a backwards compatible manner, it should be 2.47.0. If no new functionality has been added, it should be 2.46.2. So in this case it boils down to classifying the changed functionality as newly added or fixed. Specifically; is the JSON output ordering new functionality or is it what was previously specified, implemented or at least intended?
I see five points under Changed in the CHANGELOG. If these are correctly classified, the new release should be 2.47.0.
I guess this is really ambiguity on our side than within semver. It’s possible someone was depending on the previous arbitrary order of nodes in the JSON, that we are now outputting ordered. Bumping to 2.47.0 sounds like the safe option.
1 Like
MR is posted for this for anyone curious: Stable Release 2.47.0 (!1835) · Merge requests · graphviz / graphviz · GitLab
Expect Graphviz 2.47.0 on 2021-03-15.
1 Like