Roadmap

Release roadmap

Where we stand and what is coming next. The overview shows our release dates on a roughly two-month cadence, with the current development state.

Dec 25 Jan 26 Feb 26 Mar 26 Apr 26 May 26 Jun 26 Jul 26 Aug 26 Sept 26 Oct 26 Nov 26 Dec 26 Jan 27

4.2.13.0 Lord Monkey Fist

4.2.14.0 Bridge Monkey

4.2.15.0 J. Fred Muggs

4.2.16.0 Koko

4.2.17.0 Caesar

4.2.18.0 Jiggs

4.2.19.0 Nim Chimpsky

released

in progress

planned

Today · 04/06/2026

released current development planned

Each codename follows a small tradition: famous monkeys from science, pop culture and history. Current development happens in branch sid (stands for: „still in development“), which becomes the next stable release in the coming weeks.

Rollout and quality

We deploy with care and react fast when something is off.

A release date is not the day every museum gets switched over. Here is how we actually roll versions out and what happens when something goes sideways.

Wave rollout

After the release date a new version is not pushed to every installation at once. We deploy step by step and watch each environment closely. go~mus is not a simple central SaaS application but an enterprise platform with diverse, branching scenarios per museum, integration and workflow.

Testing and automation

Before every release, automated test scenarios run against the core business flows: online sales, booking flows, POS, reservations, wallet tickets, REST API. On top of that, code review on every pull request and manual tests on the staging environment. Still: at this scale, 100 % coverage does not exist.

When something does go wrong

Where software is written, bugs happen. We say that openly. When something is reported after a release we react quickly: prioritised bug fixes, hotfix deployments within hours rather than days, direct communication to the affected institutions. A release is not a point on the calendar, it is a process that continues past the date.