We’re changing how we version OutSystems 11 releases

We are adopting a new version numbering format in OutSystems 11 releases, starting with Development Environment 11.5.39.


We’ve been hearing your feedback about our current version numbering and we are now improving it. We are going to start using the most standard version numbering system: Semantic Versioning. This system is the simplest way to communicate the content of a release. For example, you can quickly identify if a new version has new features or if it contains just fixes and improvements.


The versions are now a sequence of three numbers, separated by a period, and assigned in ascending order. The new version numbering format is the following:


[Major].[Feature].[Patch]


In some places, you will see a 4th number identifying the build ID, used to identify specific builds.


Check how OutSystems versions are numbered for more details on the new version numbering schema.


Just for comparison purposes, In the previous versioning model, the Development Environment version 11.5.39 would correspond to version 11.0.539.0.


This change will have no impact on the compatibility between released versions of the Development Environment and Platform Server or LifeTime versions.

Additionally, you can check the compatibility of each Development Environment release in its download page, under the “Compatibility” section. For example, the Development Environment 11.5.39 is “Compatible with Platform Server 11, release Sep.2018 or later”.


We are gradually introducing the new version numbering format to all OutSystems 11 releases, including Platform Server and LifeTime.

In the meanwhile, you can check this page for more information on the version numbering format still followed in OutSystems 11 Platform Server and LifeTime releases, as well as in all OutSystems version 10 releases.



Q&A


Q: Why is this new versioning format better?

A: It’s easier to identify what’s included in a given release. For example, a release contains new features when the second version number increases, and it contains bug fixes and minor improvements when the third number increases.


Q: Is the new version numbering format going to be applied to previous releases?

A: No, the new version format will only be applied to new releases.


Q: Will all versions be incremental across components or will different components have independent versions?

A: Every OutSystems component (Development Environment, Platform Server, LifeTime) will have independent version numbers. Compatibility information between different components will be clearly stated in the “Downloads” page.


[Major].[Feature].[Patch].[Build]

Applying Semantic versioning (v2.0.0) and following the DevOps principle, Shall we assume that all new features (no matter platform is bundling tons of features together for a big bang release and giving it a name OutSystems 12) will keep on coming as feature release without incrementing Major. Unless this is breaking or incompatible change with the previous release.

Swatantra Kumar wrote:

[Major].[Feature].[Patch].[Build]

Applying Semantic versioning (v2.0.0) and following the DevOps principle, Shall we assume that all new features (no matter platform is bundling tons of features together for a big bang release and giving it a name OutSystems 12) will keep on coming as feature release without incrementing Major. Unless this is breaking or incompatible change with the previous release.

Hi Swatantra,

That's it. If a new release has new features we will increment the [Feature] part only of the version.

André Grossinho wrote:

Swatantra Kumar wrote:

[Major].[Feature].[Patch].[Build]

Applying Semantic versioning (v2.0.0) and following the DevOps principle, Shall we assume that all new features (no matter platform is bundling tons of features together for a big bang release and giving it a name OutSystems 12) will keep on coming as feature release without incrementing Major. Unless this is breaking or incompatible change with the previous release.

Hi Swatantra,

That's it. If a new release has new features we will increment the [Feature] part only of the version.


That's good to hear. This also means community will get benefitted with early release of features, instead of waiting for a major release. 

Cheers!