Each version number is made up from a prefix that indicates the overall development stage (as soon as the full release is reached the prefix is left out), a dash connecting the prefix with the actual version number that comes in the format of three numerals divided by dots and as whole prepended with the letter "v".
This structure is appended by the build and patch indicators in the form of a letter followed by a numeral. If no patch has been applied the numeral is left out.
In this form the version number v1.0.0r poses the first full-release version with everything from pre-alpha-v0.0.1 to beta-v9.9r9 being considered pre-release builds.
It will always follow the structure of:
[prefix]- + v[full version].[intermediate version].[iteration] + [release branch] + [patch on branch]
All pre-release version numbers begin with one of these prefixes:
pre-alphaalphabeta
Any full-release builds will have no prefix but will be constructed the same way in all other aspects.
The whole structure is v#.#.# with each "#" indicating a numeral ranging from "0" to "9" and will be used in ascending order.
The [intermediate version] numeral (the middle one) may exceed the number range by becoming two numerals.
The version number has either "d", "t" or "r" appended. When a branch version is receiving patches a numeral ranging from "1" to "9" in ascending order is appended.
- "d" indicates that it's a developement build to which a debugger and profiler can be attached
- "t" indicates a test build, the included features may and likely will contain bugs, glitches and other issues
- "r" indicates a release build, meaning that all known bugs and glitches of that version should be fixed
- sometimes a numeral might be appended to the letter, this counts the number of patches applied within the version level and type