Version numbers in print #

This page is for reporters and editors who put version numbers in copy. Exponential's numbers follow a few simple rules, and one of them surprises people: the last position keeps counting, so 0.0.4.10 comes after 0.0.4.9.

Contents #

1. Writing a version
2. Lines and releases
3. Released or in development
4. Velocity and extension numbers
5. Comparing and sorting versions
6. Common mistakes

Writing a version #

Source: Brand and naming rules.

Lines and releases #

All releases are listed on The 6.0.x releases at a glance.

Released or in development #

A version is released when its Git tag is published. Until then:

• write "<version>, which has no release tag yet" or "the next release", after checking git tag -l 'v6.0.*' --sort=version:refname;
• do not give a date unless the project has published one;
• describe features as "in the <version> changelog", not as available in a release (Covering the 6.0.15 line).

Once published, a version is never changed: "a fix for a problem in v6.0.14 or an earlier tag reaches you as the next release, not as a corrected copy of the old one" (SECURITY.md; Published versions never change).

Velocity and extension numbers #

Velocity and the extensions have their own numbers, independent of the kernel's:

• Velocity uses four positions, for example 0.0.4.54 (the first version composer.json required, on 20 October 2026).
• "After 0.1.9 the next release is 0.1.10; only the last position counts up unless you decide otherwise" (Extensions, "Release it").
• Extensions shipped inside the kernel carry the kernel's version; separate extensions carry their own.

Write the product with its number: "Velocity 0.0.4.54", "the expai extension 0.0.1.12". Do not mix them with the kernel's number.

Comparing and sorting versions #

Compare position by position as numbers: 6.0.10 is newer than 6.0.9. A plain alphabetical sort gets this wrong and puts 6.0.10 before 6.0.2. On a clone of the repository:

git tag -l 'v6.0.*' --sort=version:refname    # right order
git tag -l 'v6.0.*' | sort -V                  # right order
git tag -l 'v6.0.*' | tail -1                  # WRONG: alphabetical, may not be the newest

Common mistakes #

Related pages #

• How version numbers work
• The 6.0.x releases at a glance
• Verifying a release yourself
• Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.