Skip to content

Commit 8d1f851

Browse files
docs(wave-roadmap): single long-lived branch workflow
Per review request — all v2 architecture work lives on the one `feat/v2-architecture` branch tracked by PR #494, instead of fragmenting into per-wave sub-branches. Updates `docs/wave_roadmap.md` to encode this contract for future contributors: - Branch: `feat/v2-architecture` (single, long-lived). - PR: #494 (stays open and grows commit-by-commit). - Cadence: one commit per phase, message prefix `feat(gapXX-phaseN)`. - Per-wave milestone: checked-in `docs/gap0X_final_gate_report.md`. - Merge to main: only when GAP 01-08 are all done (GAP 05 opt-in). Refresh the title from "Post-Wave-A roadmap" to "v2 architecture roadmap" to match the broader scope. Note Wave A is now MERGED INTO the branch (not "this branch"). No code changes. Made-with: Cursor
1 parent 0a2dba6 commit 8d1f851

1 file changed

Lines changed: 12 additions & 5 deletions

File tree

docs/wave_roadmap.md

Lines changed: 12 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,20 @@
1-
# Post-Wave-A roadmap
1+
# v2 architecture roadmap
22

3-
_Last updated: at the close of Wave A (GAP 03 + GAP 04), branch `feat/v2-gap03-gap04`._
3+
_Last updated: at the close of Wave A (GAP 03 + GAP 04). All work happens on the **single long-lived branch** [`feat/v2-architecture`](https://github.com/RunanywhereAI/runanywhere-sdks/tree/feat/v2-architecture) tracked by **PR #494**._
44

5-
The seven-gap migration on `runanywhere-sdks-main` is structured as five waves. Two are done; four remain. This doc captures the **scope, dependency, and rationale** for each remaining wave at a level deep enough to start a detailed plan; full per-phase plans get written one wave at a time as the prior wave merges.
5+
The seven-gap migration on `runanywhere-sdks-main` is structured as five waves. **Two waves done, three remain (one optional).** This doc captures the **scope, dependency, and rationale** for each remaining wave at a level deep enough to start a detailed plan; full per-phase plans get written one wave at a time as the prior wave merges.
6+
7+
## Branch + PR contract
8+
9+
- **Single branch.** Every wave commits directly to `feat/v2-architecture`. Do **not** create per-wave sub-branches (`feat/v2-gap0X-*`); the previous experiment with `feat/v2-gap01-gap02` + `feat/v2-gap03-gap04` was consolidated into one branch on review request so the diff stays in one place.
10+
- **Single PR.** [PR #494](https://github.com/RunanywhereAI/runanywhere-sdks/pull/494) stays open and grows commit-by-commit as each wave lands. Reviewers see the cumulative diff; per-wave breakdown is preserved by commit messages + per-wave final-gate reports under `docs/gap0X_final_gate_report.md`.
11+
- **Per-wave milestone discipline.** Each wave finishes with (a) its `docs/gap0X_final_gate_report.md` checked in and (b) the PR description updated with a one-line entry under "What's in this PR today". No wave merges to `main` independently — the whole migration ships when GAP 01-08 are all done (GAP 05 / DAG runtime is opt-in).
12+
- **Commit cadence.** One commit per phase (the discipline established in Wave A). Commit messages follow `feat(gapXX-phaseN): <subject>` so reviewers can use `git log --grep "gap0X"` to pull out a single gap's history.
613

714
| Wave | Gaps | Status | Estimate (single eng) |
815
|------|---------------------------------------|---------------|-----------------------|
9-
| Done | GAP 01 + GAP 02 | merged | (history) |
10-
| A | GAP 03 + GAP 04 | this branch | ~4–6 wk |
16+
| Done | GAP 01 + GAP 02 | merged into branch | (history) |
17+
| A | GAP 03 + GAP 04 | merged into branch | ~4–6 wk |
1118
| **B**| **GAP 07 + GAP 06** | next | ~2–4 wk |
1219
| **C**| **GAP 09** | after B | ~3–4 wk |
1320
| **D**| **GAP 08** | after C | ~6–10 wk (parallel) |

0 commit comments

Comments
 (0)