Retire drift-prone roadmap/plan docs (work now lives in Issues + Milestones) #38

Closed
opened 2026-07-17 23:51:25 +00:00 by claude-bot · 0 comments
Contributor

All current and future-planned work has been migrated into Forgejo Issues + Milestones (v1.0.1 → v2.0.0 + Backlog). The in-repo planning/status docs now only duplicate that and are prone to drift, so they are being removed.

Removing:

  • docs/ROADMAP.md — In Progress / Planned / Under Investigation / Completed roadmap. All forward-looking items map to issues #7–#24; the "Completed" log is covered by CHANGELOG.md + git history.
  • docs/HANDOFF.md — point-in-time deployed-state snapshot + "Remaining Roadmap Items" (→ #7, #22, #8/#9, #11, #10). Manual dev-deploy/test commands are superseded by the CD workflow (.forgejo/workflows/cd.yml) and the dev-test note in agent memory.
  • docs/roadmap-spc-forecast-enhancements.md — SPC/forecast/notification-controls spec; all three phases completed (see CHANGELOG.md), forward-looking bits in #13/#14/#15.
  • SECURITY_AUDIT_REMEDIATION_PLAN.md — all 8 remediation phases implemented; "non-blocking follow-ups" tracked and closed as #4/#5/#6.

Verification before removal: each doc's forward-looking content was cross-checked against existing issues; no gaps found. No code or README.md references these files (only the docs cross-referenced each other).

Note: several issues carry a Source: docs/ROADMAP.md → … provenance line. These are historical provenance, left as-is rather than churning ~20 issue bodies.

All current and future-planned work has been migrated into Forgejo Issues + Milestones (v1.0.1 → v2.0.0 + Backlog). The in-repo planning/status docs now only duplicate that and are prone to drift, so they are being removed. **Removing:** - `docs/ROADMAP.md` — In Progress / Planned / Under Investigation / Completed roadmap. All forward-looking items map to issues #7–#24; the "Completed" log is covered by `CHANGELOG.md` + git history. - `docs/HANDOFF.md` — point-in-time deployed-state snapshot + "Remaining Roadmap Items" (→ #7, #22, #8/#9, #11, #10). Manual dev-deploy/test commands are superseded by the CD workflow (`.forgejo/workflows/cd.yml`) and the dev-test note in agent memory. - `docs/roadmap-spc-forecast-enhancements.md` — SPC/forecast/notification-controls spec; all three phases completed (see `CHANGELOG.md`), forward-looking bits in #13/#14/#15. - `SECURITY_AUDIT_REMEDIATION_PLAN.md` — all 8 remediation phases implemented; "non-blocking follow-ups" tracked and closed as #4/#5/#6. **Verification before removal:** each doc's forward-looking content was cross-checked against existing issues; no gaps found. No code or `README.md` references these files (only the docs cross-referenced each other). Note: several issues carry a `Source: docs/ROADMAP.md → …` provenance line. These are historical provenance, left as-is rather than churning ~20 issue bodies.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
rbrooks/WeatherBot#38
No description provided.