Monthly Release Notes Instead of Large Batch Releases

Not everything important happens on the publication date of a major release. Many improvements become relevant before that point and should be communicated accordingly.

That is why we are primarily changing how we communicate new features and technical improvements. What is not changing is which kinds of topics belong in minor or major releases. Instead of waiting to summarize changes only with a major version, we now communicate them through monthly Release Notes that highlight new features, improvements, and relevant technical changes in a timely way.

Why We Are Changing This

Until now, our Release Notes mainly summarized the changes since the last major version. That made sense for a traditional release cycle, but it came with one drawback: there could be a noticeable delay between an improvement becoming available and it being communicated.

At the same time, many relevant improvements do not align neatly with a single major release communication milestone. The monthly Release Notes make these changes easier to follow and communicate them closer to when they actually matter, without changing the release strategy itself.

Different Versions, One Shared Overview

Not every part of the ADITO ecosystem follows the same versioning scheme. Areas such as the Designer, AI features, or individual modules may have their own version numbers and may receive new versions between two platform releases.

That is exactly what the monthly Release Notes are meant to make visible. They show not only changes to the core platform, but also improvements in adjacent areas when they are relevant for users and developers. The version label on each entry makes it transparent from which version a specific feature is available.

What Improves for Users and Developers

Teams no longer have to wait for the next major version jump to understand what has already changed in the platform.

Classification becomes easier as well: smaller, more regular updates are easier to assess than one long accumulated list covering many months. This helps equally with planning, communication, and prioritization.

Release Notes in a New Rhythm

From now on, our Release Notes will be published monthly. They are therefore no longer just a retrospective of a major version, but an ongoing overview of what has actually arrived in the platform.

This format improves traceability and ensures that communication aligns more closely with actual release behavior. Anyone who wants to know what changed in a given month will find that information gathered in one place. At the same time, nothing changes in terms of which types of changes are delivered in minor and major versions.

The complete technical history remains available in the changelog. The Release Notes, by contrast, take on more of the role of a curated, accessible monthly overview.

What Stays the Same

More frequent communication does not mean more hectic releases. New features and improvements will still only be released once they are production-ready.

Minor versions remain focused on stability. Breaking changes, as well as features that could potentially have a greater impact on existing systems, will continue to be reserved for major versions. That has already been the case so far and does not change with the monthly rhythm of the Release Notes.

The difference lies in transparency: changes are no longer collected for longer than necessary, but are communicated when they are actually usable. This gives users and developers clearer orientation while the platform remains stable and predictable.

You can find the first monthly edition in the Release Notes for April 2026.

./Robert