docs: retire ROADMAP.md for Forgejo issues/milestones #306

Merged
jqueuniet merged 1 commit from docs/retire-roadmap into main 2026-07-23 21:52:36 +02:00
Owner

Batch 2 of the move to Forgejo-native project management (Batch 1 created the labels, 9 thematic milestones, and issues #295–#305).

Retires ROADMAP.md: work tracking → Forgejo issues/milestones, reference → docs/.

  • Move the "Known DM2 ports" 8-family table into docs/sources/overview.md as a new "Platform families" section. The per-port support matrix is dropped as redundant — overview.md (attribute matrix, family clusters, audio routing) plus the format docs already state full coverage.
  • Delete ROADMAP.md and repoint the ~7 inbound references:
    • README.md → a "Project status" pointer (forge for work, docs/ for reference).
    • docs/development.md → work tracking is on the forge; findings go in docs/.
    • "Known DM2 ports" citations (external-references.md, graphics-dat.md) → overview.md § "Platform families".
    • DM1/CSB and SWSH.DAT open items → their project milestones ("Earlier games", "Cinematics & container audio").
    • Stale ROADMAP.md citations in saves.md, music.md, and an HMP test comment dropped.
  • Add .forgejo/issue_template/{feature,bug,research}.md so new issues get type/* labels and prompt for area//port/.

Docs/comment-only; no code paths touched.

Still manual (no projects API on Forgejo 15.0.5): creating the Kanban board and dropping the issues into it.

Batch 2 of the move to Forgejo-native project management (Batch 1 created the labels, 9 thematic milestones, and issues #295–#305). Retires `ROADMAP.md`: **work tracking → Forgejo issues/milestones**, **reference → `docs/`**. - **Move** the "Known DM2 ports" 8-family table into `docs/sources/overview.md` as a new "Platform families" section. The per-port support matrix is **dropped** as redundant — `overview.md` (attribute matrix, family clusters, audio routing) plus the format docs already state full coverage. - **Delete** `ROADMAP.md` and repoint the ~7 inbound references: - `README.md` → a "Project status" pointer (forge for work, `docs/` for reference). - `docs/development.md` → work tracking is on the forge; findings go in `docs/`. - "Known DM2 ports" citations (`external-references.md`, `graphics-dat.md`) → `overview.md` § "Platform families". - DM1/CSB and `SWSH.DAT` open items → their project milestones ("Earlier games", "Cinematics & container audio"). - Stale `ROADMAP.md` citations in `saves.md`, `music.md`, and an HMP test comment dropped. - **Add** `.forgejo/issue_template/{feature,bug,research}.md` so new issues get `type/*` labels and prompt for `area/`/`port/`. Docs/comment-only; no code paths touched. Still manual (no projects API on Forgejo 15.0.5): creating the Kanban board and dropping the issues into it.
docs: retire ROADMAP.md in favour of Forgejo issues/milestones
All checks were successful
CI / msrv (1.90) (pull_request) Successful in 41s
CI / stable (pull_request) Successful in 59s
CI / audit (pull_request) Successful in 18s
CI / msrv (1.90) (push) Successful in 40s
CI / stable (push) Successful in 59s
CI / audit (push) Successful in 17s
45a15eff44
Work tracking moves to the Forgejo project (thematic milestones + area/
type/port/priority labels + a Kanban board); per-format and per-port
reference stays in docs/.

- Move the 'Known DM2 ports' 8-family table into docs/sources/overview.md
  as a 'Platform families' section (the per-port support matrix is dropped
  as redundant with overview.md + the format docs, which already state
  full coverage).
- Delete ROADMAP.md and repoint the ~7 inbound references: README gets a
  'Project status' pointer; development.md points work-tracking at the
  forge; the 'Known DM2 ports' citations go to overview.md; the DM1/CSB
  and SWSH.DAT open items point at their project milestones; stale
  ROADMAP citations in saves.md, music.md and an hmp test comment dropped.
- Add .forgejo/issue_template/{feature,bug,research}.md so new issues get
  type/* labels and prompt for area/port.
jqueuniet deleted branch docs/retire-roadmap 2026-07-23 21:52:36 +02:00
Sign in to join this conversation.
No reviewers
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
jqueuniet/dm2-tools!306
No description provided.