CerebralDatabank Versioning Scheme

The versioning scheme used for all of CerebralDatabank's products. Version: v1.1

vMAJOR.MINOR.PATCH-TYPE

where MAJOR, MINOR, and PATCH are all integers greater than or equal to 0, while TYPE is described further below.

PATCH can be omitted if it is equal to 0, and TYPE can be omitted if it is equal to "stable".

• MAJOR indicates the major release number. This increments if a major and/or backwards-compatibility breaking change is introduced.
• MINOR indicates the minor release number. This increments if a minor, backwards-compatible change is introduced. This value must be reset to 0 every time MAJOR is incremented (e.g. v2.12 to v3.0).
• PATCH indicates the patch release number. This increments if a functionality issue (bug/issue) has been fixed. This value must be reset to 0 every time MINOR is either incremented or reset to 0 (e.g. v3.8.10 to v0.9 or v3.19.4 to v4.0). This can be omitted if it is equal to 0.
• TYPE indicates the type of the version. Possible values are: "stable" (stable; working release; not recommended, omit TYPE if it's "stable"), "rc" (release candidate; beta version with potential to become a final product), "beta", and "alpha" (e.g. v1.9.8 to v2.0-alpha to v2.0). Optionally (however not recommended), a positive integer can be added to the end of TYPE (e.g. v2.3-beta3 or v2.3-beta.3). When MAJOR is equal to 0, TYPE can also indicate the tpe of the version indicated, for example v0.9.2-beta would indicate that v0.9.2 is a beta, instead of being the beta version that precedes v0.9.2.
• In cases where there are space or size constraints for the version, it is acceptable to use abbreviations for TYPE, such as v2.0a instead of v2.0-alpha, v3.5.6b3 instead of v.3.5.6-beta3, and v4.5rc2 instead of v4.5-rc2. It is highly recommended to use the full words and hyphen whenever possible.

Valid version names: