Skip to content

Rewrite LTS, MTS documentationt #11074

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
MarkvanMents wants to merge 2 commits into
base: development
Choose a base branch
from
Open

Rewrite LTS, MTS documentationt #11074

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
67898d0
Rewrite LTS, MTS documentationt
MarkvanMents Apr 23, 2026
76690fe
CHecked other documents and tidies up with AI review.
MarkvanMents Apr 23, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions content/en/docs/releasenotes/mobile/native-support.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ Native mobile apps built using a Mendix LTS version are supported for 15 months

### Mid-Term Support Version (MTS)

Native mobile apps built with a Mendix MTS version are supported for 15 months from the official release date, unless an LTS version of the same Mendix major version is released earlier. In that case, support ends 3 months after the release of the LTS version. This support period is up to 6 months shorter than standard Mendix support durations.
Native mobile apps built with a Mendix MTS version are supported for 15 months from the official release date, unless an LTS version of the same Mendix major version is released earlier. In that case, support ends 3 months after the release of that LTS version. This support period is up to 6 months shorter than standard Mendix support durations.

### Monthly Release Version

Expand All @@ -39,6 +39,6 @@ Following this recommendation provides the following benefits:
* **Reduced update effort**, as smaller, more frequent updates involve fewer changes
* **Access to the latest features and improvements** available in Mendix Studio Pro

As an alternative, you can choose to skip every other MTS version and update your native mobile app once per year. With this approach, you must still update to the LTS version as soon as it is released.
As an alternative, you can choose to skip every other MTS version and update your native mobile app once per year. With this approach, you must still update to an LTS version as soon as it is released.

Consider this update path as an example of what you could do: Mendix 10 LTS {{% icon name="chevron-right" %}} Second Mendix 11 MTS {{% icon name="chevron-right" %}} Mendix 11 LTS
102 changes: 42 additions & 60 deletions content/en/docs/releasenotes/studio-pro/lts-mts.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,27 +8,15 @@ weight: 1

The goal of this document is to clarify Mendix Studio Pro version options and help you decide which version to run your applications on.

To understand the different types of versions and releases, consider the example of Studio Pro [11.6.1](/releasenotes/studio-pro/11.6/#1161) and see the sections below.
To understand the different types of versions and releases, consider the example of Studio Pro [11.6.1](/releasenotes/studio-pro/11.6/#1161) discussed in the sections below.

### Major Version {#major-version}

In the 11.6.1 example, the first number (**11**) indicates the major version.

Mendix supports three major versions at a time. To clarify our current offering and in relation to our SLA, today Mendix supports major versions 9, 10, and 11.
Mendix supports three major versions at a time. To clarify our current offering and in relation to our SLA, while the current major version is Mendix 11, Mendix supports major versions 9, 10, and 11.

As of Mendix 10, to make planning version upgrades easier for our users, Mendix will release in a two-year cadence, which means that every two years we plan to release a new major version in June. This will help in preparing and planning to adopt new releases and upgrade older Mendix versions. Each major version release will start with two public [beta releases](/releasenotes/release-status/).

For Mendix 10 and 11, we are planning to follow this release timeline:

| Release | Date |
| --- | --- |
| 10.24 LTS | June 2025 |
| 11.0 GA | June 2025 |
| 11.6 MTS | December 2025 |
| 11.12 MTS | June 2026 |
| 11.18 MTS | December 2026 |
| 11.24 LTS | June 2027 |
| 12.0 GA | June 2027 |
Comment on lines -21 to -31
Copy link
Copy Markdown
Collaborator Author

@MarkvanMents MarkvanMents Apr 23, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removed and replaced with a description of how to see whether a version in LTS or MTS by looking at the tag on release notes and in Marketplace.

As of Mendix 10, to make version support duration clearer for our users, Mendix has released a new major release in a two-year cadence. Every two years in June, Mendix releases a new major version. This helps you to prepare and plan to adopt new releases and upgrade older Mendix versions. Each major version release may start with public [beta releases](/releasenotes/release-status/) to obtain feedback from users.

### Minor Version

Expand All @@ -42,110 +30,104 @@ In the 11.6.1 example, the third number (**1**) indicates the patch version.

A patch version is released on an as-needed basis. It includes security fixes and critical bug fixes, but it does not include new features or breaking changes (unless these address security issues).

## Long-Term Support Version (LTS) {#lts}
## Types of Support

There are three types of minor release which have different periods of support. These are long-term support versions (LTSs), medium-term support versions (MTSs) and other minor versions.

These three types of support are described below.

Both LTS and MTS versions are production-grade and fully supported for production use. LTS versions are supported for the longest period of time, allowing to upgrade at a slower pace.
### Long-Term Support Version (LTS) {#lts}

An LTS version is the last minor release of a major version. Its release is aligned with the GA release of the next major version. For example, the 10.24 LTS version was released in the same month as Mendix 11 GA. Once a minor version becomes an LTS, it will not have new features added to it.
An LTS version is a minor release of a major version which will continue to be supported until the major version falls out of support. LTS versions are production-grade and supported for the longest period of time, allowing a slower pace to your upgrades.

Although it continues to be supported, once a minor version becomes an LTS, it will have bug and security fixes only and not have new features added to it.

Release notes for the current LTS versions are marked with an LTS badge (<text class="badge badge-pill badge-lts" style="margin-left:0px">LTS</text>) in the left sidebar. The Marketplace also indicates LTS versions in the same way.

These are the current LTS versions of Studio Pro:

* [9.24](/releasenotes/studio-pro/9.24/) (started in March, 2023)
* [10.24](/releasenotes/studio-pro/10.24/) (started in June, 2025)

Release notes for the current LTS versions are marked with an LTS badge (<text class="badge badge-pill badge-lts" style="margin-left:0px">LTS</text>) in the left sidebar.

Recommended LTS upgrade Cycle: 2 to 4 years.

{{% alert color="info" %}}
Mendix recommends using the latest patch version of the release as the latest version will contain the latest fixes.
Mendix recommends using the latest patch version of the LTS minor version as this will contain the latest fixes.
{{% /alert %}}

### Support Duration
#### Support Duration

Support for an LTS version ends when a third consecutive major version is released for general availability (for example, support on version 8 ended with the GA release of version 11).
Support for an LTS version ends when a third consecutive major version is released for general availability (for example, support for Mendix version 8 ended with the GA release of Mendix version 11).

This diagram illustrates the LTS concept with version and [end of support](#end) examples:

[//]: # (Original image in Powerpoint /static/originals/refguide/lts-support.pptx)
[//]: # (Original image in PowerPoint /static/originals/refguide/lts-support.pptx)

{{< figure src="/attachments/releasenotes/studio-pro/lts-mts/lts.png" class="no-border" >}}

{{% alert color="info" %}}For details on extending support for an older major version, see the [Extended Support](/support/#extended-support) section in *Mendix Support*.{{% /alert %}}

{{% alert color="info" %}}For details on the shorter support durations of native mobile apps, see [Support Guidelines for Native Mobile](/releasenotes/mobile/native-support/). We recommend updating native apps a bit more often than other mobile apps so you can advantage of evolving features. {{% /alert %}}
{{% alert color="info" %}}Native mobile apps have a shorter support duration. See [Support Guidelines for Native Mobile](/releasenotes/mobile/native-support/) for more information. We recommend updating native apps more often than other mobile apps and web apps so you can take advantage of evolving features. {{% /alert %}}

### Release Cycle
#### Support with Patch Releases

An LTS starts with the release of a new higher major version for general availability. For a description of Mendix’s major release cadence, see the [Major Version](#major-version) section above.
For the support duration, the LTS will receive [patch](#patch-version) releases only.

For an LTS version, there will only be [patch](#patch) releases on an as-needed basis.
#### Upgrading Impact

### Support with Patch Releases
Upgrading from an LTS to an LTS often has a lower impact than other upgrade options. That is because an LTS has the longest support duration and only gets critical fixes, which results in high stability over time. In addition, moving from one LTS to another happens less often as there are fewer LTS versions compared to [MTS](#mts) versions or monthly release versions.

For the support duration, the LTS will receive patch releases only.
### Medium-Term Support Version (MTS) {#mts}

### Upgrading Impact

Upgrading from an LTS to an LTS often has the lowest impact compared to other upgrade options. That is because an LTS has the longest support duration and only gets critical fixes, which results in high stability over time. In addition, depending on how rigorous your application update/release process is, the upgrade would only have to be done once, as opposed to multiple times between MTS versions or monthly release versions.

## Medium-Term Support Version (MTS) {#mts}

MTS versions are production-grade and give teams access to new capabilities on a regular cadence. A new MTS version is released every 6 months within the same major version, keeping upgrades straightforward. You can also skip one or more MTS cycles to fit your team's schedule.
MTS versions are also production-grade and give teams access to new capabilities on a regular cadence. A new MTS version is released more often than an LTS within the same major version, keeping upgrades straightforward. You can also skip one or more MTS cycles to fit your team's schedule.

For example, version 11.6 is an MTS version which was released in [December, 2025](#major-version).

Release notes for any current MTS versions are marked with an MTS badge (<text class="badge badge-pill badge-mts" style="margin-left:0px">MTS</text>) in the left sidebar.
Release notes for any current MTS versions are marked with an MTS badge (<text class="badge badge-pill badge-mts" style="margin-left:0px">MTS</text>) in the left sidebar. The Marketplace also indicates MTS versions in the same way.

Mendix MTS versions offer a balance between getting the latest and greatest Mendix has to offer every month, and security and stability.

Recommended MTS upgrade cycle: 6 to 18 months.

{{% alert color="info" %}}
Mendix recommends using the latest patch version of the release as this will contain the latest fixes.
Mendix recommends using the latest patch version of the MTS minor version as this will contain the latest fixes.
{{% /alert %}}

### Support Duration
#### Support Duration

Support for an MTS version ends three months after the LTS version of that major version is released.
Support for an MTS version ends three months after the next major version is released. For example, support for 10.6, 10.12, and 10.18 MTS versions ended three months after Mendix version 11 was released.

### Release Cycle

MTS versions are introduced as minor versions approximately every 6 months after a new major version release for general availability. There will only be patch releases for an MTS on an as-needed basis.

### Support with Patch Releases
#### Support with Patch Releases

For the support duration, the MTS will receive patch releases only.

### Upgrading Impact
#### Upgrading Impact

The impact of upgrading between MTS versions is higher than upgrading between LTS versions. That is because an MTS has a shorter support duration than an LTS, which means it has less time to become as stable as an LTS version. In addition, the upgrade has to be done approximately every six months.
The impact of upgrading between MTS versions is higher than upgrading between LTS versions. That is because an MTS has a shorter support duration than an LTS, which means it has less time to become as stable as an LTS version. In addition, the upgrade has to be done more frequently.

## Monthly Release Version {#patch}
### Monthly Release Version {#patch}

A monthly release is a non-MTS/LTS minor release that only receives patches for critical/security issues if they can be released earlier and faster than the next minor version release.

### Support Duration
#### Support Duration

Monthly release versions do not enjoy regular patch releases like MTS and LTS versions do. Most bugs found in monthly release versions are resolved in the subsequent monthly release. However, high impact bugs which are found before the next minor (monthly) release may lead to a patch release.

For example, if a bug is found in version 10.1.0 before version 10.2.0 is released, it will usually only be fixed in the next monthly release, that is version 10.2.0. If the bug is judged to have a high impact and can be fixed quickly, then a patched version 10.1.1 may be released.

### Release Cycle
#### Release Cycle

This is a monthly release that includes new features as well as security patches that are applied to existing MTS and LTS versions.
This is a monthly release that includes new features as well as bug fixes and security patches. Mendix applies security patches and bug fixes to existing MTS and LTS versions, but not new features.

### Support with Patch Releases
#### Support with Patch Releases

A monthly release only receives patches for critical/security issues if they can be released earlier and faster than the next minor version release. Otherwise, bugs found in a monthly release will only be fixed rolling forward to the next minor version.

For example, if you are using version 10.1.0 after 10.2.0 has been released and you find a critical issue in 10.1.0, that fix will only be released in the next monthly release, which would be 10.3.0.

If a bug is found in a monthly-release version for an older major version, it will only be fixed as a patch on the existing LTS (for example, a bug found in 10.16 will only be fixed for a patch release on the LTS version 10.24).
If a bug is found in a monthly-release version for an older major version, it will only be fixed as a patch on an existing LTS (for example, a bug found in 10.16 will only be fixed for a patch release on the LTS version 10.24).

#### Upgrading Impact

### Upgrading Impact
The impact of upgrading between monthly releases is the highest of these options. That is because every month, all new features are shipped in such minor versions, including all bug fixes and security patches. In addition, to keep up with security patches and bug fixes, the upgrade has to be done monthly, which can be a significant drain on resources.

The impact of upgrading between monthly releases is the highest of these options. That is because every month, all new features are shipped in such minor versions, including all bug fixes and security patches. In addition, the upgrade has to be done monthly, which can be a significant drain on resources.
The advantage is that you can immediately use new features without having to wait for the more stable MTS/LTS version.

## End of Support {#end}

Expand Down