Naming scheme for SQL/MX releases

SQL/MX contains many individual products, which are identified by T-numbers. A release name identifies a set of products as belonging to a given SQL/MX release.

Each release is identified by a three-part release identifier. The following is an example of a release identifier:

Release identifier
  1. The first number indicates a major release, which introduces major new functionality and a new SQL version.

  2. The second number indicates an incremental release, which introduces an incremental change and some new functionality.

  3. The third number indicates a maintenance release, which introduces bug fixes and minimal new functionality.

The upgrade risk increases from maintenance to major releases because major releases introduce significant new functionality that makes fallback more difficult, if implemented.

The first and second levels of the release name (for example, SQL/MX Release 3.5) are based on the product version identifier (for example, L35). Major and incremental releases typically change the product version of SQL/MX. Maintenance releases and time-critical fixes (TCFs) do not change the product version of SQL/MX.