The versioning scheme uses the format: MAJOR.MINOR.PATCH

  • MAJOR: API incompatible changes will increase this number. Changes that expect the database to be at a minimum version will also increase this number.
  • MINOR: addition of new large features or important modification of existing features will change this number. Features impacted by the changes are always QCed through complete regression testing for each minor release.
  • PATCH: bug fix releases will increment this number. We also create patches when adding minor functionality.

With this format, API and updates compatibility will be guaranteed for the same MAJOR version number.