Why MAME is 0.288 stable while the manual says 0.289
On July 28, 2026, MAMEdev's release page names 0.288 as the latest official release while the online manual identifies 0.289 development documentation. That does not make an Android port 0.289. Trust the port's explicit upstream revision or build record, match content and tools to that revision, and use rolling documentation only when the described option actually exists in the target build.
Do this in order
- 01
Open the official MAME release page and record the latest stable number and release tag rather than relying on a search snippet.
- 02
Read the version printed by the Android port or core and look for its upstream MAME revision, source link, and build date.
- 03
Treat the online manual's 0.289 label as rolling development context, not proof that any installed Android binary contains that code.
- 04
Match romset definitions, chdman, command options, and bug evidence to the installed upstream revision.
- 05
If a documented option is missing, check the target build's own help or menu before assuming a bad install; the port may be older or omit the interface.
- 06
Test one authorized game, save the exact version matrix, and change the app, core, tools, or content only one layer at a time.
Decision and diagnostic table
| Version surface | What it proves | What it does not prove |
|---|---|---|
| MAMEdev 0.288 release page | Latest tagged official release on the review date | Version inside an Android port |
| Online manual labeled 0.289 | Current development documentation state | Availability of 0.289 stable binaries |
| Android app or core version screen | Claim made by that packaged build | Source revision unless the port identifies it |
| Official source tag or commit | Exact upstream code identity | That a third-party APK was built faithfully or safely |
Release and documentation clocks differ
MAME follows a monthly release process, while the public manual can advance with development. During that window, a stable user can legitimately see a manual version one step ahead of the official release page.
Use the stable tag's documentation when exact option names or defaults matter. A rolling page is useful context but must not silently redefine the installed binary.
Android adds another version boundary
MAMEdev publishes official Windows binaries and source packages, not an official Android APK on its release page. Android products are ports, derivatives, or cores with their own packaging and update policy.
A trustworthy port states the upstream revision and provides source and license information. A marketing name such as current, latest, or 2026 is not a machine-definition version.
Version identity controls reproducibility
Romset hashes, parent relationships, device definitions, CHD expectations, configuration options, and diagnostic output can change between releases. Record the emulator/core, tools, and content definition as one matrix.
When reporting a bug, include the port version and upstream revision if known. Do not report rolling-manual behavior against an unidentified Android build as though both were the same artifact.
MAME's software license and source availability do not grant rights to commercial ROM, BIOS, CHD, artwork, or music. Match versions only with your own lawful dumps or explicitly authorized releases.