gsadmin/pulse
1
0
Fork 0
mirror of https://github.com/rcourtman/Pulse.git synced 2026-09-10 02:25:56 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix stale v6-rc-cut active-target reference in control-plane doc

Browse Source 
The `Current State` section of `docs/release-control/internal/CONTROL_PLANE.md`
still described `v6-rc-cut` as the active engineering target and listed
`v6-rc-stabilization` as planned. The active target has been
`v6-rc-stabilization` since the first governed RC shipped, and
`documentation_currentness_test` now fails on that drift. Update items 2, 4,
and 5 to match the current governed state.
This commit is contained in:
rcourtman
2026-04-16 22:57:37 +01:00
parent b19991f4ae
commit 6ec64c55ed
1 changed files with 10 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/release-control/internal/CONTROL_PLANE.md
+10 -8
View File
@@ -236,18 +236,20 @@ user language should update the control plane.
## Current State
1. v6 is the current active release profile.
2. `v6-rc-cut` is the current active engineering target.
It is a release target, so default slice selection should stay centered on
prerelease blockers, RC-publication judgment, and the remaining proof needed
before a real governed RC should actually be cut.
2. `v6-rc-stabilization` is the current active engineering target.
It is a post-RC stabilization target, so default slice selection should stay
centered on keeping Pulse v6 simple, accurate, and cleanly readable around
the proven monitoring-first floor of the shipped RCs, while broader
control-plane expansion stays out of the default target until it is proven.
3. `v6-product-lane-expansion` remains planned and is still blocked on the
broader surfaced product case being proven.
Its candidate-lane surface remains available in `available_candidate_lane_queue`
plus the linked `candidate_lanes` and `coverage_gaps`.
4. `v6-ga-promotion` remains planned and must stay dormant until a real
governed RC has actually shipped and been validated.
5. `v6-rc-stabilization` remains planned and should only become active once
the first governed RC exists.
4. `v6-ga-promotion` remains planned and must stay dormant until the shipped
RCs have been validated enough to clear the stabilization floor and the
`rc-to-ga-promotion-readiness` gate.
5. `v6-rc-stabilization` is now the active target, promoted after the first
governed RC shipped.
6. Its files remain under `docs/release-control/v6/`.
7. The existing v6 control surfaces are still live, but they now sit underneath
an evergreen Pulse control plane rather than pretending to be the whole