[FR] - Change versioning back to `major.minor.patch`

IntersectMBO / cardano-cli

This repository contains sources for the command-line interface (CLI) tool for interacting with the Cardano blockchain.

Apache License 2.0

39 stars 14 forks source link

[FR] - Change versioning back to `major.minor.patch` #834

Closed gitmachtl closed 1 month ago

gitmachtl commented 2 months ago

Not sure why this started in first place, but can we go back to versioning of just x.y.z ?

Is there a reason we see version bumps like 9.0.0.0 to 9.0.0.1?

Normally its major.minor.patch version, so not sure why we need a "sub-bugfix" number and can't go back to semantic versioning?

Martin

smelc commented 2 months ago

cc @Jimbo4350

carbolymer commented 2 months ago

We're following the versioning process described here: https://github.com/IntersectMBO/cardano-api/blob/main/RELEASING.md#version-bumping Tl;dr: In our case it's cardano-node-major-version.major.minor.patch.

gitmachtl commented 2 months ago

ok, hmm. than why is the node still major.minor.patch ?

not 100% why we need to distinguish between those two:

8.4.1.3 - if there are only backwards-compatible bug-fixes
8.4.2.0 - if there are only backwards-compatible features or bug-fixes

if they are both backwards-compatible

smelc commented 2 months ago

@gitmachtl> just FYI there is a cultural thing going on here, that Haskell has its own versioning policy called PVP. I personally believe this is a mistake that the Haskell ecosystem is doing, we should use semver but :shrug: