docs: add v2 rollout playbook for future tool rollouts - #58
Merged
Conversation
Captures the pattern used for the 2026-04-17→2026-04-18 v2.0.0→v2.0.1 rollout across 27 consumer repos. Structured as four phases (harden source, bellwether PRs, admin batch, lock+dependabot) with pitfalls, timings, and adaptation guidance for future tools (e.g., ralph-burndown). Placed under docs/plans/ next to the other planning documents. No code impact; doc-only change.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Doc-only addition. Captures the pattern used for the 2026-04-17 → 2026-04-18 v2.0.0 → v2.0.1 rollout across 27 consumer repos — structured as four phases (harden source, bellwether PRs, admin batch, lock+dependabot) with pitfalls, timings, and adaptation guidance.
Written specifically with ralph-burndown in mind as the next target, but generic enough to apply to any shared-tool rollout.
Expected CI behavior on this PR
docs/plans/*.md. Under v2.0.1 classification (docs/*), this is doc-only — the Claude review should short-circuit withVERDICT: SKIPPED (doc-only diff, 1 file(s))in ~15s.Adjacent docs
Fits next to:
docs/plans/2026-03-06-centralize-claude-assistant.mddocs/plans/2026-03-06-prompt-injection-hardening.mddocs/plans/2026-03-20-migrate-all-repos-to-blocking-review.md🤖 Generated with Claude Code