All code uses + Semantic Versioning. + The numbering scheme divided into 3 blocks (herein referred to + as Block 0, Block 1, and Block 2, in left-to-right order); the + version blocks are separated by periods. When a version number + block is incremented, all blocks to the right of it are reset to + 0. The legacy versioning scheme was a similar numerical + versioning scheme which lacked standardisation.
+Block 0 contains the MAJOR version;
+ this number is incremented whenever an API-incompatible change
+ is made to the code.
Block 1 contains the MINOR version;
+ this number is incremented whenever an API-compatible,
+ substantial change is made to the code, such as adding a
+ feature.
Block 2 contains the PATCH version;
+ this number is incremented whenever an API-compatible,
+ unsubstantial change is made to the code, such as fixing or
+ optimising the code.
Development and pre-release versions are suffixed with
+ a hyphen, followed by their phase, a period, then the version of
+ that phase; for example, -alpha.n for an
+ alpha version, -beta.n for a beta
+ version, and -rc.n for a release
+ candidate version, with n being a
+ non-negative integer. Stable versions have no suffix.
There are 4 phases of development. Each phase typically has + its own branch in each source code repository. The phases are as + follows: +
When development of a new version has begun, the code within + the alpha phase is rebased onto the most recent code from the + stable phase before work commences. This cycle continues for the + lifetime of the code.
+This list contains the policies and practices of my services.