Skip to main content

Release and Support Lifecycle

This page explains how ADITO platform releases are published and how long major and minor releases remain supported.

Release cadence​

ADITO publishes new releases monthly. Several times per year, a new major release is published. Between major releases, minor releases are published for the current major release.

What goes into a minor or major release​

Minor releases are intended for changes that can be introduced in an isolated and manageable way within the current major release line. This includes new features, bug fixes, and general improvements, as long as they do not require breaking migration steps and do not create broad upgrade risks across the system.

Major releases are used for breaking changes and for changes with larger system-wide impact. This includes cases where existing behavior no longer works as before, where functions are removed or restricted, where manual upgrade or migration steps are required, or where a change cannot be treated as an isolated enhancement because it may affect the overall system behavior.

This means:

  • Breaking changes belong in a major release.
  • Changes that require manual action during upgrade belong in a major release.
  • Large cross-cutting or system-wide changes belong in a major release.
  • New features, bug fixes, and smaller improvements belong in the current minor release when they can be added in an isolated and controlled way.

Minor release end of life​

Within a major release line, only the latest available minor release is supported.

As long as a major release line is the current one, its minor releases may receive bug fixes and new features.

Examples:

  • When 2026.0.4 is released, support for 2026.0.3 ends and moves to 2026.0.4.
  • If no further minor release is published for 2026.0, the latest released 2026.0.x version remains supported until the 2026.0 major release line reaches end of life.

Support after the next major release​

Once the next major release is published, the previous major release line remains supported, but only in a limited maintenance mode.

In this phase, previous minor releases no longer receive regular feature development. Updates for that release line are limited to important bug fixes, for example:

  • regressions
  • security-relevant fixes
  • other critical corrections

This means that new features are delivered in the current major release line, while the previous major release line only receives high-priority fixes.

Major release end of life​

A major release remains supported until the corresponding successor major release is published in the following year. Once that successor is published, the previous major release reaches end of life (EOL) and is no longer supported.

Examples:

  • The major release 2026.0 remains supported until 2027.1 is released.
  • Once 2027.1 is released, 2026.0 reaches EOL and is no longer supported.

Practical example: ADITO 2026.0​

For the major release 2026.0, the following support rules apply:

  1. If 2026.0.4 is released, support for 2026.0.3 ends.
  2. If no later 2026.0.x release is published, the latest available 2026.0.x release remains supported.
  3. Until 2026.1 is released, 2026.0.x may receive both bug fixes and new features.
  4. After 2026.1 is released, 2026.0.x only receives important bug fixes, such as regressions or security-relevant fixes.
  5. Support for the entire 2026.0 release line ends when 2027.1 is released.