Skip to main content

Versioning

Although all mos.components have their own release number, some are linked to a cartain extent by the reference to the corresponding mos.language version. These components include:

  • mos.language
  • mos.server
  • mos.client
    • mos.android
    • mos.iOS

Official versions

The release number of mos.language is only two characters long e.g. 5.2, whereas that of the official release verisons of the mos.client i.e. mos.android and mos.iOS as well as mos.server is always four characters long e.g. 5.2.4.1, with the first two characters corresponding to the current mos.language version.

The mos.client release number 5.2.4.1 would therefore mean:

  • 5.2 mos.language version

    • 5 mos.language major version
    • 2 mos.language minor version
  • 4.1 mos.client version

    • 4 mos.client feature version
    • 1 mos.client extra version

While the mos.server release number 5.2.3.6 would mean the following:

  • 5.2 mos.language version

    • 5 mos.language major version
    • 2 mos.language minor version
  • 3.6 mos.server version

    • 3 mos.server feature version
    • 6 mos.server extra version

While every new mos.language version automatically requires new client verisons, a new mos.server version is not necessarily required.

Hotfixes

Hotfixes are versions outside the regular release cycle that cannot be postponed to the scheduled regular release for various reasons. These versions have a hotfix appendix added to the current regular release number.

A hotfix release number would therefore look like this: 5.2.4.1-hotfix1, where hotfix1 is the hotfix version.

Compatibility

Each of the components should always be compatible down to the latest mos.language major version.
This means that the mos.client android version 5.3.6.9 is compatible with the mos.language verisons 5.3, 5.0 and all versions in between. The same applies to mos.server versions.

A complete list of which mos.component versions are compatible with each other and which mos.server or mos.client versions are required as a minimum for which mos.language version is planned.

Release cycle

The regular releases follow fixed intervals, which differ depending on the type of release.

release typerelease interval
mos.language majorannually (1/year)
mos.language minorquarterly (4/year)
mos.servermonthly (1/month)
mos.clientbiweekly (2/month)