Version Numbering

Reference

https://semver.org/

Basics

MAJOR.MINOR.PATCH

• MAJOR : different MAJOR versions are incompatible, large-scale upgrades of API

• MINOR: retain source and binary compatibility with minor versions

  • new version can introduce new functions, new contents and deprecate existing functions

  • can deprecate function (remain available, removed next major version)

• PATCH: perfectly compatible forward and backwards

Library before 1.0.0 is not subject to the guideline (API can freely change)

Pre-release

Examples:

• 1.0.0-alpha,

• 1.0.0-alpha.1

Use

• Start initial development at 0.1.0 (for rapid development), and only increase minor version for each subsequent release, until

• Stable for production and have a stable API, push to 1.0.0