Release Policy

Releases

The MOSEK version numbering consists of four numbers: major.minor.build.revision. For example version 7.1.0.55 has the major version number 7, the minor version number 1 and build 0 and revision 55.

  • Major version: A new major version contains new features, major enhancements and performance improvements. Moreover, supported platforms and tools, e.g. Java version, can change in a major release. Some, but few incompatibilities with previous versions can be expected.
  • Minor version: A new minor release contains new features and efficiency improvements. Compatibility with the previous releases of the same major version has high priority.
  • Build number: A new build implies a change in how the software is built (for instance a different compiler). Mostly unused.
  • Revision: A new revision includes bug fixes and in some cases new functionality. Strong emphasis is given on backwards compatibility with existing releases of the same minor version. New revisions are released frequently.

This implies that all versions with the same major version number behave almost identically. In general it is safe and easy to upgrade to a newer version with same major version number. Some work can be expected when upgrading to a new major version but performance improvements can be expected. See release notes on the documentation page.

MOSEK supports a major version at least 2 years after the next major version is released. For instance MOSEK version 7 is supported 2 years after the initial release of MOSEK version 8. For versions without active support no new releases of the software are issued.

Major Release Dates

Version Date Active Support
8 27-may-2016 Yes
7 16-may-2013 Yes
6 01-sep-2009 No
5 01-jun-2007 No
4 03-mar-2006 No
3 01-sep-2003 No