Tag a new release

[mtibben]

Could you tag a new stable release so that distributions like homebrew can pick up the new features recently added?

Suggestions:

• update the M2G_VERSION
• use Semantic Versioning (instead of CalVer, because CalVer is better suited to large or constantly-changing projects, and SemVer is the most common way to version CLI tools)
  • tag previous releases with the semver scheme
    • e52585b at v1.2.0
    • efcfb5c at v1.5.0
    • 656a5a9 at v1.6.0
    • master at v1.7.0

[merkys]

Switching from CalVer to SemVer is problematic as some distribution management software will not understand that 1.7.0 is newer than 2021.11.06, take Debian for example where all version comparisons are done in SemVer manner.

[0x5c]

#34 would be good to get in a release too

[mtibben]

calver seems to have been introduced in 2018 however the binary continues to self-report the version as 1.5 (see M2G_VERSION)

Switching from CalVer to SemVer is problematic as some distribution management software will not understand that 1.7.0 is newer than 2021.11.06, take Debian for example where all version comparisons are done in SemVer manner.

Maybe then it's just roll forward with calver? In any case, a new release would be great

[mtibben]

@lindenb if you want me to help out cutting a release feel free to give me appropriate access and I will action

[0x5c]

Switching from CalVer to SemVer is problematic as some distribution management software will not understand that 1.7.0 is newer than 2021.11.06, take Debian for example where all version comparisons are done in SemVer manner.

This wouldn't be the first project to do such a versioning scheme change; distros already have tools/mechanisms to handle that.

[merkys]

This wouldn't be the first project to do such a versioning scheme change; distros already have tools/mechanisms to handle that.

You are right, this is doable, although it involves some additional work on distro side.