Announcements about the products, the portal and the terms they are supplied under.
Three security advisories for hosts that accept work from other hosts, a record of sign-ons and privilege changes in the system log, a scheduler that stays up when a worker is lost, and every command able to say exactly what it is.
This year's work reaches both products on every platform we build for: a security fix for linked hosts, an rpm upgrade that keeps the service running, and the tar installer brought level with the packages.
Packages now carry a signature, a bill of materials and a record of what they were built from - and a release is refused unless the fuzz tests, the upgrade tests and the vulnerability check all pass on the exact source commit.
SLES 15 and openSUSE Leap 15.6 are verified and released again for both products, Raspberry Pi OS is built as a Debian package, and POWER and IBM Z builds are available on request.
The Xi-Text spooler's first recorded revision is dated 27 September 1989. The history runs from there to this month's release without a gap.
Customers asked for a longer commitment than 2030 before they would plan around Xi-Batch and Xi-Text. The horizon is now at least 2035.
Fifty-eight articles on running Xi-Batch and Xi-Text, moved off the old platform into a maintained source and corrected against the products they describe.
In the portal, a licence entitles a system to the release it was licensed for; a support contract in force entitles it to the current one.
A deliberate campaign across every command and service - privilege changes that fail closed, bounded copies, and checks on everything arriving over the wire.
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.
Downloads, licences and the machines they are issued against, in one place - signed into with your account reference and the address we already hold. No serial number, no password.
Install Xi-Batch and Xi-Text with the system's own package manager, and let it handle upgrades, removal and what is on the machine.
Every file for the latest build of your products, listed with checksums, available without waiting for anyone to send them.
The R-numbered line ends and both products move to semantic versioning, starting on the distributions customers were actually asking for.
