Skip to main content

Roadmap, Changelog and Release Status

Last updated: August 21, 2026

The portal publishes two development records. The Roadmap shows active, upcoming and completed tracks; the Changelog lists releases, fixes, improvements and creative updates as they ship. Between them they answer most "is this finished?" questions — but only if read in their own words. Both pages carry their own status language and their own dates, and those are part of the claim. A track described as upcoming is not a commitment to a date, and an item on the Changelog is a record that something happened, not a guarantee that it still works the same way today.

Reading the two together

The Roadmap is forward-looking and provisional by nature: items move, merge and occasionally leave. The Changelog is backward-looking and stable: entries are not rewritten because plans changed. When the two seem to disagree, the Changelog describes what exists and the Roadmap describes what is intended.

Quoting development status safely

Preserve the page's own wording and date. "Listed as active on the Roadmap as of date" is defensible; "coming in the next release" is not, unless the page says exactly that. Avoid converting a roadmap position into a launch date, a feature list into a specification, or a completed track into a support guarantee. If a vertical's own interface contradicts a roadmap item, the interface wins — the roadmap describes intent at the portal level, not the current state of every surface.

Neither page is a service status board. If something is failing right now, that is a support question rather than a roadmap one, and the vertical itself is the place to check.

Official source

Canonical source for this subject: Tales of Xdripia. Checked 21 August 2026 — where this guide and the live service disagree, the service is right.