Hi BIRD folks!

Could you please consider using consistent semantic versioning in your release numbers? (see semver.org)

Up until 2.13 all releases used the x.y.z format, with a trailing .0 for the first release in each minor release. However the the 2.13 and 2.14 releases did not - they just used x.y

This broke our deployment code that uses semantic version aware checks to tell whether the running daemon is not the same as the available package.

A formally adopted (and documented) version numbering policy would be of great use to system administrators.

thanks,

Ray

Reply via email to