Loading
docs(roadmap): sync beta.md with the W39 results
What
The weekly sync of docs/roadmap/beta.md for W39 (2026-09-21 – 2026-09-27), following the
file's own ### Weekly sync workflow. The input is the
W39 results note.
Stacked on !2921 (merged), which
renames closed-beta.md to beta.md. Merge !2921 (merged) first. This MR targets its branch and retargets to
main once it lands.
| Area | Change |
|---|---|
| Header, throughput, review queue | W39: 157 merged, 57 releases, queue 44 → 32, oldest !1598 (closed) at 44 days |
| Scope table | S30 16/25, S31 13/19, S32 17/20, S17 Phase 6 41/42 plus the new virtual upstream list plan (12/21), monolith/S07 8/14 |
| Gate | Still 1. Both of #1326 (closed)'s MRs merged, so it is open pending verification |
| Readiness | readiness!85 merged 2026-09-21 |
| Gantt | Virtual bar counts, a bar for the upstream list plan, PREP marked merged, externally gated bars moved to the sync date |
Two things to check
- Dates now come from
spine.md, so two passages in !2921 (merged) changed. unified-artifact-management!151 (merged 2026-09-23) records Public Beta 2026-10-06 and GA January 2027 (19.8) as firm. "spine.mdcarries no open-beta phase" and "GA early 2027, to be confirmed" are replaced with those dates. The sync workflow's Step 10 says not to add GA dates. This edit updates a date !2921 (merged) already added, and cites Product's source. - Two links to the S17 virtual upstream list plan are absolute URLs. The plan is on
main, but !2921 (merged)'s branch is 152 commits behindmainand does not have it, so relative links faillychee. They can go back to relative links after a rebase.
This MR needs a rebase onto !2921 (merged). !2921 (merged) was rebased onto main and took review fixes on
2026-09-28, including the spine.md date handling this MR also touches. On rebase, take !2921 (merged)'s
version of the stage dates, the GA row and the spine.md passage, and keep only the W39 figures
here.
Related to #1416 (closed)
Edited by Jaime Martinez