PoolRotater Wiki

Your guide to automatic osu! multiplayer

User Tools

Site Tools


updates:v7_3_3

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
updates:v7_3_3 [2026/10/25 22:04] – v7.3.3 release, ratings and Taiko documentation wikidocsupdates:v7_3_3 [2026/10/26 00:00] (current) – v7.3.3 release, ratings and Taiko documentation wikidocs
Line 1: Line 1:
 ====== v7.3.3 release notes ====== ====== v7.3.3 release notes ======
  
-===== Live rollout under review — October 25 =====+===== Live rollout checkpoint — October 25 =====
  
-v7.3.3 is published, but production acceptance is incomplete. One live host committed the new runtime registration and then held at configuration preparation before startup. Its configuration hashes are unchanged, and a guarded remote completion also refused. Local read-only diagnostic evidence is needed to identify the cause. This is distinct from the earlier pre-admission controller-interruption test.+v7.3.3 is running on the owner host and both community hosts. The owner now runs Catch on Lobby 1, a Taiko automatic-difficulty pilot on Lobby 3, and Mania 4K on Lobby 4. Lobby 2 remains reserved/private and stopped. Existing settings were preserved; the owner intentionally changed only Lobby 3's mode and activated the new signed catalog bindings. Current links and settings are on [[status:start|Live Lobbies]].
  
-Keep held state intact. Do not reinstall, clear ownership or repeat startup to bypass this guard. The owner update is deferred; the existing Catch and 4K rooms remain on v7.3.2. The selected Lobby 3 Taiko pilot and actual Taiko gameplay remain pending.+The Taiko pilot's startup, chat access, map selection, queue, website artwork/settings and Discord panel are verified. Actual Taiko player gameplay has not yet been observed. Its NoMod normal-speed catalog and the latest Standard catalog are activated.
  
 +One community host's Standard transfer stopped at about 94%. Its configuration remained unchanged, but its independently pinned v7.2.6 recovery reader could not dispatch the newer controller contract. Completion through the already-installed v7.3.3 native entry resumed the verified partial download and restored its two intended rooms. Reporting, ratings and updater status are healthy. Bounded transfer retries and recovery-pin refresh are being validated for a follow-up release; those new changes are not yet published. The separate earlier pre-admission interruption test remains a documented limitation.
  
-**v7.3.3 is published on GitHub.** The normal installed technical acceptance passed on H (v7.3.0) and I (v7.3.2), 2 of 2. A separate extra B pre-admission controller-interruption case failed before the incoming code could run; it remains unaccepted and is a known limitation. The signed pilot feed now offers v7.3.3 to supported existing hosts; safe automatic rollout is underway. 
  
 ===== Taiko ===== ===== Taiko =====
updates/v7_3_3.1792965866.txt.gz · Last modified: by wikidocs

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki