Skip to content

📝 Docs: drop milestone-based planning guidance#523

Merged
jbourdin merged 1 commit intodevelopfrom
docs/remove-milestone-guidance
May 6, 2026
Merged

📝 Docs: drop milestone-based planning guidance#523
jbourdin merged 1 commit intodevelopfrom
docs/remove-milestone-guidance

Conversation

@jbourdin
Copy link
Copy Markdown
Owner

@jbourdin jbourdin commented May 6, 2026

Summary

  • Remove milestone instructions from CLAUDE.md (issue creation + board ordering). Add an explicit "do not assign milestones" line.
  • Drop the Milestones (Phases) section from docs/roadmap.md (4 tier tables + completed list). The kanban board remains the planning surface.

Phase milestones still exist in the repo for now (not closed) but are no longer referenced in the docs and won't be assigned on new issues.

Test plan

  • Skim CLAUDE.md Project Tracking section — reads naturally without milestone references.
  • Skim docs/roadmap.md — flows from board overview directly to feature catalogue without orphan links.
  • No remaining "milestone" references in CLAUDE.md / docs/roadmap.md / docs/standards/version_control.md / docs/standards/release_process.md (only the explicit "do not assign milestones" line in CLAUDE.md is intentional).

Phase milestones exist in the repo but are not used as a planning
structure. Drop the milestone instructions from CLAUDE.md (issue
creation + board ordering) and remove the Milestones (Phases) section
from docs/roadmap.md. The kanban project board remains the source of
truth for prioritization.
@jbourdin jbourdin merged commit d6dce19 into develop May 6, 2026
5 checks passed
@jbourdin jbourdin deleted the docs/remove-milestone-guidance branch May 6, 2026 06:53
@sentry
Copy link
Copy Markdown

sentry Bot commented May 6, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant