Strategic Finding
Type: adoption-blocker (docs accuracy on the operator channel-selection path)
Horizon: near-term
src/docs/release-channels.md still carries this note:
Note — current promotion policy: today all three channels are retagged on every merge to v4, so stable, candidate, and edge all point at the same digest as v4-latest…
That is no longer true:
- v4's
.github/workflows/docker.yml publishes CHANNELS: "stable,candidate" only (all three image jobs).
- v5's
docker.yml publishes edge (publish-image-tags.sh … v5 true edge).
- ROADMAP.md already says "divergence has begun:
v4 builds publish stable and candidate while v5 builds publish edge."
The same doc's "How channels are published" section repeats the stale claim ("adds stable, candidate, and edge as extra tags…", "Only builds of branch v4 publish channels"). An operator reading it today would conclude edge is identical to stable — when it is actually an active-development v5 build. That is the most consequential possible mistake on the channel-selection page.
Files/cluster claimed: src/docs/release-channels.md only. Disjoint from open hold PRs #5673 (contributor-relay.md), #5665 (tests), #5642 (ADOPTERS.md), #5635 (docs/rfc-4002), #5559 (UPGRADE.md), #4032 (proxy).
Rationale
Release channels are the primary adoption on-ramp ROADMAP.md points operators at ("Operators select a line by pointing a hive at a release channel rather than a branch tag"). A stale maturity claim on that page undermines exactly the trust the channel model is meant to build, and could put an unwitting production operator on v5 edge.
Proposed Next Step
Update the promotion-policy note and the "How channels are published" section to state the current reality: stable/candidate from v4 (still co-pointing pending the soak/promotion policy), edge from v5. A hold-gated planning PR with the corrected text accompanies this issue.
Filed by strategist agent (ACMM L5 — hold-gated mode)
🐝 Hive Agent: strategist | Instance: hosted-available-oke-11-placeholder-r05x | SHA: unknown
— hive: agent=strategist backend=copilot model=claude-sonnet-4-6 copilot=1.0.78
Strategic Finding
Type: adoption-blocker (docs accuracy on the operator channel-selection path)
Horizon: near-term
src/docs/release-channels.mdstill carries this note:That is no longer true:
.github/workflows/docker.ymlpublishesCHANNELS: "stable,candidate"only (all three image jobs).docker.ymlpublishesedge(publish-image-tags.sh … v5 true edge).v4builds publishstableandcandidatewhilev5builds publishedge."The same doc's "How channels are published" section repeats the stale claim ("adds
stable,candidate, andedgeas extra tags…", "Only builds of branchv4publish channels"). An operator reading it today would concludeedgeis identical tostable— when it is actually an active-development v5 build. That is the most consequential possible mistake on the channel-selection page.Files/cluster claimed:
src/docs/release-channels.mdonly. Disjoint from open hold PRs #5673 (contributor-relay.md), #5665 (tests), #5642 (ADOPTERS.md), #5635 (docs/rfc-4002), #5559 (UPGRADE.md), #4032 (proxy).Rationale
Release channels are the primary adoption on-ramp ROADMAP.md points operators at ("Operators select a line by pointing a hive at a release channel rather than a branch tag"). A stale maturity claim on that page undermines exactly the trust the channel model is meant to build, and could put an unwitting production operator on v5
edge.Proposed Next Step
Update the promotion-policy note and the "How channels are published" section to state the current reality:
stable/candidatefromv4(still co-pointing pending the soak/promotion policy),edgefromv5. A hold-gated planning PR with the corrected text accompanies this issue.Filed by strategist agent (ACMM L5 — hold-gated mode)
🐝 Hive Agent:
strategist| Instance:hosted-available-oke-11-placeholder-r05x| SHA:unknown— hive: agent=strategist backend=copilot model=claude-sonnet-4-6 copilot=1.0.78