6.3.0 is published, so the pages that were waiting for it say so: Linux is released rather than "in the tree", the write surface has a release number, and the version that never existed is gone
The Linux page opened with a banner saying the port was in the tree and not
yet released, and that the first release to carry packages would be "the next
one". That release is 6.3.0 and it went out on 10 September 2026, so the
banner now points at it and the install commands name the packages that are
actually on the release page rather than a version number nobody can download.
Five places named 6.2.29. There is no such version and there never will be -
the release after 6.2.28 is 6.3.0, and README.md already says why - so the two
package filenames, the two "since 6.2.29" notes about relative directory
values and the Installation paths diagnostic's label all move to 6.3.0.
The API reference's route tables gained the write surface a day before the
release but nothing in them said which release it belonged to, while the rows
around them carried 6.2.27 and 6.2.28. A reader could reasonably have read the
settings, rules and certificate routes as shipping in 6.2.27, which is half
true and the misleading half: those routes could only be read then. Section 4
now says which routes arrived in 6.3.0 and why the method column is the one to
read, and the scope note names the units the write surface was split into.
The landing page's At a glance table was stale in five of its rows: the
release and its build number, the platform (Windows only, when the whole point
of 6.3 is that it is not), the administration surfaces, the suite's size and
the wiki's own page count. The route count was stale in a way worth recording:
it said 65, which matched neither the number of rows in the reference table nor
the number of distinct paths at the commit it was written from, so it is now
82 routes over 68 paths, both countable from the page it points at.
The Control Panel reference said "the latest, v6.2.28", and one thing under
ControlPanel did move in 6.3.0: the sign-in box's user name is a literal again
(#156), which is why a fresh installation in Chinese could not sign in. The
page says so, with the twenty-one files that differ between the tags.
The footer stamped 6.2.28 on all fifty-one pages.
The REST API writes: the route tables on the REST and API Reference pages carry the settings groups, the rules, the routes, the aliases, the account update, the certificates and listeners and the restart in place, with what each refuses and who may call it
The Installing on Linux page's suite row and the Regression Test Environment page's "On Linux" section say what the write surface changed for the Linux run: 278 of 319 pass where 233 did, and what still skips is a COM-only call or the suite's fake DNS zone rather than a route that does not exist.
The regression suite on Linux: the Installing on Linux page's suite row says what runs (319 of 2,135 tests, 233 passing, 86 skipped for named API gaps, 0 failing, and CI on every push), and the Regression Test Environment page gains an "On Linux" section with the variables, the test-tree recipe and the command
The section is the one hmailserver/docs/RegressionEnvironment.md carries at f18c38a04. A first draft of this page edit had appended an older copy of the whole page around the new section (338 lines became 630); this is the committed page plus the sixty lines of the section, inserted before "When a run is interrupted".
Linux: an Installing on Linux page from the packages to a delivered message, the relocation runbook as a page, the Installation paths diagnostic in the Monitoring table, the domain routes on the REST page, and the platform notes the Settings and Capabilities pages needed