Versioning Convention

We follow a structured naming convention for all releases to ensure clarity, traceability, and consistency across deployments.

The convention itself is maintained in a spreadsheet:

In short

A release is identified by two things:

  • A version number of the form vYY.MM[.PATCH]: the year and the month of the quarter’s primary release, with an optional patch number. For example v25.10.0.

  • A codename, taken in alphabetical order: Basic, Apricot, Barberry, Cherry, and so on.

Each release is tagged in Git with its version number, and the number is recorded in the VERSION file at the root of the platform repository.

For the list of releases and which codename maps to which number, see Current & Past Versions.