General purpose code and programs follow the major.minor format, ommitting the patch numeral of standard semantic versioning. The major is incremented when a non-backwards compatible API change has been made, or if moving from 0 (incomplete) to 1 (feature-complete). The minor is incremented when significant but backwards-compatible changes have been made. The version numbering may also be reset entirely if a program is majorly overhauled.
The major.minor numbering is prefixed with v and suffixed with either -alpha or -beta if the major is 0 to denote varying levels of functionality.
Program release naming follows the Release major.minor format, where major.minor is replaced with the version of the program (as noted above) being released.
Documents follow the rev-n format, where n is the number of the current revision of the document.