PoolRotater Wiki

Your guide to automatic osu! multiplayer

User Tools

Site Tools


updates:v7_0_7

Differences

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

Link to this comparison view

updates:v7_0_7 [2026/10/16 01:14] – Refresh v7.0.5–v7.0.8 release status and audited public GitHub availability wikiadminupdates:v7_0_7 [2026/10/16 06:39] (current) – Document v7.1 shared statistics, consent, private diagnostics and verified v7.0.7 owner rollout wikiadmin
Line 1: Line 1:
 ====== v7.0.7 — owner room-retirement repair ====== ====== v7.0.7 — owner room-retirement repair ======
  
-^ Status | Qualified and queued for the owner's all-three-rooms-empty controller window; not yet live at the October 15, 2026 Pacific review |+^ Status | Running in the owner's three configured rooms; verified October 15/16, 2026 Pacific time |
 ^ Baseline | Exact owner v7.0.5 installation; this is not the operator v7.0.6 update bundle | ^ Baseline | Exact owner v7.0.5 installation; this is not the operator v7.0.6 update bundle |
  
Line 13: Line 13:
  
 ===== Current owner rollout ===== ===== Current owner rollout =====
-The owner's fixed Standard, Mania 4K and Mania 7K rooms remain on v7.0.5 while this controller change waits for all three to become empty and idle together. The intentionally disabled automatic Standard room is outside that topology. Occupied rooms are not closed to create an update window, and existing settings, titles, authorization, Discord, website integration, catalogs and votes are preserved.+The owner's fixed Standard, Mania 4K and Mania 7K rooms have completed the controller upgrade to v7.0.7. Automatic Standard remains intentionally disabled. Existing settings, titles, authorization, Discord, website integration, catalogs and votes are retained. Fresh [[status:start|room status]] provides current observations; this page records the dated rollout review.
  
 This owner-only artifact must not be installed over the independent operator's v7.0.6 runtime: it does not carry that runtime's complete automatic-updater files. [[updates:v7_0_8|v7.0.8]] is the separately qualified distributed successor. A numerically newer owner repair is not automatically a compatible operator package. This owner-only artifact must not be installed over the independent operator's v7.0.6 runtime: it does not carry that runtime's complete automatic-updater files. [[updates:v7_0_8|v7.0.8]] is the separately qualified distributed successor. A numerically newer owner repair is not automatically a compatible operator package.
  
 ===== Validation and limits ===== ===== Validation and limits =====
-Affected liveness, terminal-event, maintenance and protected-update checks passed, followed by installed full-catalog donor qualification with invented external events. Checks cover normal retirement, occupied siblings, unknown ownership and canceled-target refusal/recognition. These results do not establish live deployment; the existing queue and fresh [[status:start|room status]] provide rollout evidence.+Affected liveness, terminal-event, maintenance and protected-update checks passed, followed by installed full-catalog donor qualification with invented external events. Checks cover normal retirement, occupied siblings, unknown ownership and canceled-target refusal/recognition. The later protected-controller review also confirmed v7.0.7 active; isolated tests and live observations remain distinct evidence.
  
 [[updates:v7_0_5|Current owner resilience release]] · [[updates:v7_0_8|Operator repair]] · [[updates:start|Release history]] [[updates:v7_0_5|Current owner resilience release]] · [[updates:v7_0_8|Operator repair]] · [[updates:start|Release history]]
  
updates/v7_0_7.txt · Last modified: by wikiadmin

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki