Manuals built with the release, and one name for every file
The four manuals are built from source with every release and listed in the portal, and every package, tar and manual now carries the same naming scheme.
Two changes to what a release contains, both aimed at the same thing: knowing what you have got.
The manuals ship with the release
The Administrator's Guide, User Guide, Reference Manual and API manual are built from their sources as PDFs with every release and listed in the portal beside the packages. They are a product of the release rather than a document updated afterwards, so the manual on the portal describes the release next to it.
(The Xi-Batch Quick Guide was built the same way until 20 July 2026, when it was folded into the User Guide.)
One naming scheme
Every rpm, deb, tar and manual is named the same way:
<product>-<blend>-<version>+<build>-<cpu>-<make>-<osname>.<ext>
The products are xibatch and xitext. The scheme means a filename on a
machine, in a change record or in an email identifies exactly what it is - which
product, which build, which platform - without anyone having to open it.
Alongside it, one rule for the numbers: the semantic version is the software, and a per-platform packaging revision counts up under the same version when only the packaging has changed. A re-packaged release is visibly a re-package rather than looking like new software.
Downloads and licensing · Reading an Xi version number and distribution file name