Release version policy

• The version number is in A.B.C format, where A is the “major” version, B is the “minor” version, and C is the “patch” version.
• Incrementing only the last number would mean full backward compatibility.
• Create a beta pre-release (A.B.CbD, where D is the "beta" version) 1 month before an official release to allow other developers to test the compatibility of their packages.

Versions examples:

• Release
  • 1.2.0
  • 1.2.1
• Pre-release
  • 1.2.1b1
  • 1.2.1b2

References:

Best Practice: Build Prerelease Packages