Versioning

A version number takes the form MAJOR.MINOR.PATCH where each level is non-negative integer and increase numerically by increments of one.

For example: 0.0.1 -> 0.0.2 -> 0.1.0 -> 0.1.1 -> 0.1.2 -> 1.0.0 -> 1.0.1 -> 1.0.2

PATCH level must be incremented if only backwards compatible internal changes are introduced.

MINOR level must be incremented if new, backwards compatible functionality is introduced to the public API. It must be incremented if any public API functionality is marked as deprecated. It may include PATCH level changes. PATCH level must be reset to zero when MINOR level is incremented.

MAJOR level must be incremented if any backwards incompatible changes are introduced to the public API. It may include MINOR and PATCH level changes. PATCH and MINOR level must be reset to zero when MAJOR level is incremented.

MAJOR version zero (0.MINOR.PATCH) is for initial development. Anything may change at any time. The public API should not be considered stable.