Roadmap

Roadmap

The authoritative, up-to-date roadmap lives in to-dos/ROADMAP.md in the repository, and is intentionally not duplicated here — a wiki copy would drift out of sync with the canonical file the moment either one changed. This page is a pointer, plus the ticket-numbering convention every commit and PR in this project follows.

Ticket IDs

Every work item has a stable, citable ID of the form T-PPSS-NNN:

• PP — a 2-digit phase number
• SS — a 2-digit sprint number within that phase
• NNN — a 3-digit ticket sequence within that sprint

For example, T-0001-003 is phase 0, sprint 1, ticket 3. These IDs are referenced directly in commit messages and PR descriptions, and stay stable across the ticket's whole lifecycle from planning through release.

Where "current state" actually lives

Three files, each with one clear job, referenced in this order:

1. docs/STATUS.md — the single source of truth for per-suite pass counts, the board tier matrix, and version policy. If you want to know exactly where the project stands right now, this is the file.
2. CHANGELOG.md — the full release-by-release detail for every shipped version.
3. to-dos/ROADMAP.md — the forward-looking plan: phases, sprints, and open tickets.

Release cadence

Rusty2600 follows Semantic Versioning: additive feature work ships as MINOR releases, breaking changes as MAJOR, fixes as PATCH. Every release ships through a real GitHub pull request with CI results and automated review-bot comments adjudicated (fixed, dismissed with documented reasoning, or explicitly deferred) before merging — see Architecture-Decision-Records for the kind of documented-reasoning decisions that shape what does and doesn't get built.

See also

Deferred-Features · Reference-Materials · Architecture-Decision-Records