You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/deployment/mendix-cloud-deploy/zero-downtime.md
-4Lines changed: 0 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,9 +19,7 @@ With ZDT, Mendix Cloud intelligently manages the deployment process, ensuring yo
19
19
To leverage the benefits of zero-downtime deployment, your Mendix application and deployment environment must meet the following criteria:
20
20
21
21
***Mendix runtime version** – Must be running on Mendix Runtime version 10.24 or above.
22
-
***Application instances** – The application must be configured to run with a single runtime instance.
23
22
***Change type** – The deployment must involve only [configuration-level changes](/developerportal/deploy/zero-downtime/#zdt-application).
24
-
***Deployment platform** – Must be deployed on Mendix Cloud(Kubernetes).
25
23
26
24
{{% alert color="info" %}}
27
25
No special setup is required to enable ZDT. When your application and deployment meet these prerequisites, ZDT is automatically available for eligible changes.
@@ -71,11 +69,9 @@ During these types of updates, Mendix Cloud performs the deployment in a way tha
71
69
Zero-downtime deployment will not apply under the following conditions:
72
70
73
71
* Mendix Runtime versions below 10.24
74
-
* Application runs with more than one runtime instance
Copy file name to clipboardExpand all lines: content/en/docs/releasenotes/deployment/mendix-cloud/2026.md
+10Lines changed: 10 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,6 +8,16 @@ weight: 1
8
8
9
9
## March 2026
10
10
11
+
### March 15, 2026
12
+
13
+
#### Improvements
14
+
15
+
*[Zero-downtime deployment](/developerportal/deploy/zero-downtime/) now supports multiple runtime instances without service interruption. Previously, this feature was only available for applications with a single runtime instance.
16
+
17
+
#### New Features
18
+
19
+
* Environments on Mendix Cloud are now labeled **Unlicensed** one day after the contract expires.
Copy file name to clipboardExpand all lines: content/en/docs/releasenotes/studio-pro/lts-mts.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,7 +44,9 @@ A patch version is released on an as-needed basis. It includes security fixes an
44
44
45
45
## Long-Term Support Version (LTS) {#lts}
46
46
47
-
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.
47
+
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.
48
+
49
+
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.
48
50
49
51
These are the current LTS versions of Studio Pro:
50
52
@@ -53,12 +55,10 @@ These are the current LTS versions of Studio Pro:
53
55
54
56
Release notes for the current LTS versions are marked with an LTS badge (<textclass="badge badge-pill badge-lts"style="margin-left:0px">LTS</text>) in the left sidebar.
55
57
56
-
Mendix advises using LTS versions for all production apps, as LTS versions of Studio Pro enjoy the highest security and stability. LTS versions also have the longest support duration compared to other versions.
58
+
Recommended LTS upgrade Cycle: 2 to 4 years.
57
59
58
60
{{% alert color="info" %}}
59
-
60
61
Mendix recommends using the latest patch version of the release as the latest version will contain the latest fixes.
61
-
62
62
{{% /alert %}}
63
63
64
64
### Support Duration
@@ -91,18 +91,18 @@ Upgrading from an LTS to an LTS often has the lowest impact compared to other up
91
91
92
92
## Medium-Term Support Version (MTS) {#mts}
93
93
94
-
An MTS is a minor version released approximately every 6 months after a new major version release for general availability.
94
+
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.
95
95
96
96
For example, version 11.6 is an MTS version which was released in [December, 2025](#major-version).
97
97
98
98
Release notes for any current MTS versions are marked with an MTS badge (<textclass="badge badge-pill badge-mts"style="margin-left:0px">MTS</text>) in the left sidebar.
99
99
100
100
Mendix MTS versions offer a balance between getting the latest and greatest Mendix has to offer every month, and security and stability.
101
101
102
-
{{% alert color="info" %}}
102
+
Recommended MTS upgrade cycle: 6 to 18 months.
103
103
104
+
{{% alert color="info" %}}
104
105
Mendix recommends using the latest patch version of the release as this will contain the latest fixes.
0 commit comments