rcourtman 478a03b9ed Describe releases as the fixed release train everywhere ...

Since 4 October 2026 releases are mechanical: the release train cuts the
next minor from main 14 days after the last stable (or earlier on
request), soaks the release candidate on Preview for 24 hours, and
promotes it unchanged unless an open release-blocker issue stops it.

The shipped release docs, the promotion policy, the checklist, the source
of truth, several governance pages and two workflow comments still
described the retired model: release lines, steward judgment, 72-hour
soaks, a nightly rehearsal and patch releases scheduled by severity.
State the train's rules once, in the Release Train section of the
promotion policy, checked against the train itself, and point the rest
at it. Remove the unused internal copy of the promotion resolver, which
still enforced the old 72-hour soak.

2026-10-06 12:06:18 +01:00

..

AGENT_VALUES.md

docs(agents): add customer support communication guidance

2026-08-11 16:39:36 +01:00

CONTROL_PLANE.md

Describe releases as the fixed release train everywhere

2026-10-06 12:06:18 +01:00