Complete RC11 release acceptance
This commit is contained in:
@@ -534,7 +534,17 @@ maritime freshness evidence classifies all three fixed official editions as
|
||||
|
||||
## RC-11 - Final release package
|
||||
|
||||
**State: in progress.**
|
||||
**State: complete.**
|
||||
|
||||
The release-candidate gate passed 1,030 backend tests and 16 frontend tests,
|
||||
frontend typecheck/build, offline and live migration validation, isolated
|
||||
fresh install, checksum-verified backup, isolated restore/upgrade and an
|
||||
actual previous-image rollback plus forward deployment. Belgium/North Sea
|
||||
release journeys and the 390/1366/2560 UX audit passed against port 1202.
|
||||
Python/npm policy, SPDX SBOM and the container policy scan passed with zero
|
||||
reachable fixed HIGH/CRITICAL findings. The exact tagged commit, immutable
|
||||
image and detached SSH signature are bound in the external checksummed release
|
||||
manifest.
|
||||
|
||||
### Work
|
||||
|
||||
@@ -562,7 +572,7 @@ maritime freshness evidence classifies all three fixed official editions as
|
||||
|
||||
## Current autonomous phase
|
||||
|
||||
Continue with RC-11. Build and validate the final immutable release candidate,
|
||||
retain the RC-10 dry-run-only cleanup posture, prove fresh install, upgrade,
|
||||
restore and rollback, and close only after the tagged image passes live
|
||||
Belgium/North Sea browser acceptance.
|
||||
RC-0 through RC-11 are complete. No separate RC-12 phase exists. Continue only
|
||||
with bounded post-RC work explicitly selected from the known limitations; do
|
||||
not reinterpret a jurisdiction's `partial`, `not_configured` or `unsupported`
|
||||
coverage as release success.
|
||||
|
||||
Reference in New Issue
Block a user