This project uses $SOME_CUTE_VERSIONING_SCHEME_NAME. It works like this:
Version numbers have the short form:
<major>.<minor>
Functionality can be either stable or unstable. Stable features are not subject to breaking changes, even in major version upgrades.
Unstable features fall in to four categories: alpha, beta, deprecated, and internal.
Alpha features are subject to breaking changes at anytime and without warning.
Beta features may experience breaking changes, but the goal is for them to stabilize, and so such breakage will be accompanied by guidance.
Deprecated features will be removed in the next major version release. Warning and a migration plan will be provided.
Internal features are also subject to breaking changes at anytime. They differ from alpha features in that they are not expected to stabilize.
When the major version is 0, it is called the "alpha release". All features are considered alpha, unless explicitly declared otherwise. Even if designated stable, functionality in an alpha release should should be treated as beta at best.
For major version 1 and up, all documented features are considered stable, unless otherwise indicated. All undocumented functionality is considered internal.