Skip to main content
This matrix maps backend builds to documentation versions, keyed on backend_calver. Each backend_calver is globally unique and appears in exactly one row. For the version string format and who owns each segment, see Versioning logic.

​
How to look up compatibility

  1. Find your backend build’s backend_calver in the Compatibility table.
  2. That row’s documentation version describes your build.
  3. If your backend_calver isn’t listed, the build hasn’t been reviewed yet. Ask in #technical-writing.
  4. If your backend_calver is earlier than 20240301, the build predates the versioning scheme and no documentation version describes it. See note (1).

​
Documentation versions

​
Compatibility

​
Legend

Documentation version types
  • Stable: released documentation version with no quality tag.
  • Pre-release: documentation version with a quality tag (ALPHA, BETA or RC). Not validated for production.
  • Not available: legacy version with no entry in the version dropdown.
Build statuses
  • Supported: tested; the documentation version accurately describes this backend build.
  • Supported with caveats: tested; accurate with limitations described in the notes.
  • Untested: listed but not yet reviewed. Do not rely on this mapping.

​
Notes

  1. v1 predates the tree-name scheme and has no backend_calver, so it cannot be looked up by calver. It is referenced here by its legacy label only and is not retrofitted with a tree name.

​
Maintenance

  • Every new backend_calver triggers a matrix review and gets its own row.
  • Each backend_calver appears in exactly one row. A documentation version can cover multiple backend_calver values.
  • No cell is left blank; use ”—” where a value does not apply.
  • Rows are never deleted. Every status change is recorded in the changelog below with a date and reason.