Add configurable beta test plans and staged rollout
This commit is contained in:
@@ -39,6 +39,11 @@ without a Docker health check use their running state as the readiness signal.
|
||||
|
||||
## How restarts stay safe
|
||||
|
||||
Betas support configurable gameplay, participation, stability and manual-review
|
||||
requirements, saved presets, coverage rules and staged rollout. See
|
||||
[Beta test plans](docs/beta-test-plans.md) for usage and the session telemetry
|
||||
contract used by round and custom-feature checks.
|
||||
|
||||
File changes are staged sequentially. Their activation uses rolling restarts:
|
||||
by default only **one server across the fleet** can restart or recover at a
|
||||
time. Promotions, rollbacks, drift reconciliation, and beta restarts share this
|
||||
|
||||
Reference in New Issue
Block a user