Skip to content

Roadmap

DoubleGate edited this page Oct 16, 2026 · 2 revisions

Roadmap

Planning entry point: to-dos/ROADMAP.md. Versioning policy and history: VERSION-PLAN.md. One plan per release: to-dos/plans/. What has shipped: CHANGELOG.md.

Where things stand

The current release is v3.2.0 "Confluence" (2026-10-15). v3.0.0 "Cornerstone" (2026-10-06) was the API major: it gathered every breaking change since v2.x and added an emulation epoch for movies and netplay (ADR 0043, ADR 0045). v3.0.1 and v3.1.0 followed, and v3.2.0 is built on them.

The planned line (plans, not releases)

Everything below is a plan recorded in the repository, drafted on 2026-10-07 in to-dos/plans/v3.1-to-v4.0-line-plan.md. Scope, numbering and order can change; the plan files are the reference.

  • v3.3.0 to v3.8.0: emulator accuracy themes alongside phases of the MiSTer FPGA core's development, verified in simulation. The v3.3.0 plan is the next slot.
  • v3.9.0: a feature freeze for the FPGA core and a release-candidate pair, mobile signing set up, and preparation for v4.0.0.
  • A hardware release at the end of v3.9.x: the FPGA core run on a SuperStation One and the mobile apps run on real devices, then free store listings (v3.x-hardware-verification-plan.md).
  • v4.0.0: the remaining public enums made #[non_exhaustive], and feature parity for the FPGA core.

A format break no longer requires a major version; a change that alters emulated output raises the emulation epoch instead (VERSION-PLAN.md).

The MiSTer FPGA core

A sibling project is writing a new NES core in SystemVerilog from public documentation, using RustyNES as its verification oracle (ADR 0037, docs/mister.md). Its bitstreams are release candidates: no hardware has run any of them yet, so a booting core on real hardware is not claimed.

Two meanings of "v2.0"

Older documents mention an engine-lineage "v2.0" master-clock milestone. That work shipped inside the v1.0.0 production core and is not a RustyNES release. RustyNES's own v2.0.0 "Timebase" (2026-07-03) is a different milestone, which replaced the dot-lockstep scheduler with the current one (Scheduler).

Items that were considered and deferred are tracked on Deferred-Features.

Clone this wiki locally