Looking to understand what your version of Mendix Studio means and more about the release cycles for Mendix Studio Pro? Keep reading!

What each number in your version of Mendix Studio Pro stands for

First things first, what does each section of a Mendix Studio Pro version indicate? Great question!

The first number will show you what the major version is associated with your Mendix Studio Pro. A major version is typically released every 18 months and includes new features and fixes, but can also include breaking changes. What is a breaking change? These are larger changes that can require modifications to your application.

The second number will show you what the minor version is for your Mendix Studio Pro. A minor version will be released every month generally and will include new features and fixes as well, but does not include any breaking changes.

The third number will show you the patch version associated with your Mendix Studio Pro. A patch version gets released on an as-needed basis and does not include new features or breaking changes, but rather is for security and critical bug fixes.

What each version type means

Now that we know what each number in our specific Mendix Studio Pro indicates, let’s talk more about each release cycle and how each version is supported.

Let’s first discuss our Long-Term Support (LTS) version. This will be the latest minor version before a new major version is released. What exactly does this mean for your application? As the LTS will have the highest security and stability, along with the longest support, we’d suggest you use this version for all Production applications. There is also no regular release cycle associated with the LTS, as only patches are released on an as-needed basis.

Next up we have our Medium-Term Support (MTS) version. The MTS is a minor version and is released approximately every six months after the major version is released. Following this track will allow you to take the patch releases of the MTS to continue to get the latest and greatest Mendix has to offer each month. One thing to note is that the MTS has a shorter support duration than the LTS and therefore has less time to become stable. Why is the support shorter? The MTS depends on the creation of the latest LTS and major version release. Once a new major version has been released, the newest MTS for the older version is now the new LTS.

Lastly, we have the Monthly Release version. These versions are released quickly on a monthly basis with the critical and security patches applied to the LTS and MTS, and with new features. The most important thing to consider when choosing this option is that patch versions are not released. If any fixes are required, they will be released in the next Monthly Release version. An exception to this would be if a critical or security patch is required and can be released before the next minor version release. Then this patch will be provided for the Monthly Release version.

What the risk is for upgrading to each version type

So, you understand the release cycle for each version type now and how they’re supported, but how can you decide which track is the right fit for you?

Transitioning from one LTS to another LTS will have the lowest impact on your application. Why you may ask? Since the LTS has the longest support duration and receives only critical fixes, it is the most stable option. Additionally, you will have plenty of time to prepare for this transition as it would only need to occur when the next major version has been released.

The MTS to MTS upgrade schedule is a bit more rigorous. If you want to upgrade based on this release cycle, you will be performing your upgrades approximately every six months. This option has a higher impact than the LTS transition because each MTS has a shorter period to become as stable.

Using the Monthly Release version upgrade cycle has the highest impact on your application. What makes this a risky option? Since there is a new version released each month with all the new features, bug fixes, and security patches, there is less stability with these versions. An additional thing to consider when looking at this option is that upgrading monthly can have a significant drain on your resources.

What it means when support has ended for a version

Now that we have gone over all the ways new versions of Mendix Studio Pro are released, let’s talk about what happens to the older versions.

Support for the oldest LTS will end after the third consecutive major version is released. For example, support for Mendix Studio Pro version 6 ended when version 9 was released. What does this mean? When a version is transitioned out of support, there will no longer be fixes, updates, investigations, troubleshooting, or assistance for this version.

When a version does reach the point that support has ended, we recommend uninstalling these versions. Though you can continue to use these versions after they are no longer supported, this would be at your own risk and we do not recommend this.

What to do if you want more details

Still looking for more information on the Mendix Studio Pro versioning and release cycle? Take a look through the documentation here for additional details.