Software versioning

There are three main categories of software versions in IXIASOFT CCMS: major version, minor version, and service pack/ hot fix. These different categories of software versions are tracked in the version number, which changes as software updates are released in these different categories.

The version number is written as as major-version.minor-version.build-number, for example:

Example version number
These are defined as follows:
  • Major: The major number increases (for example, from 6.x.xxx to 7.x.xxx) when there are significant changes in the functionality or its components that require an important upgrade of the deployment. These include a major upgrade of the underlying framework (Java, Eclipse, etc.), an operating system that is no longer supported, a major update of the IXIASOFT TEXTML Server version, etc. A new major software version may introduce changes that are not compatible with the configuration of an older version. In this case, an upgrade procedure is provided.
  • Minor: The minor number increases (for example, from 6.1.xxx to 6.2.xxx) to introduce new important features. A minor update may require configuration changes and upgrades of the components. A new minor software version may introduce changes that are not compatible with the configuration of an older version. In this case, an upgrade procedure is provided.
  • Build number: The build number increases (for example, from 6.1.140 to 6.1.155) to introduce bug fixes through service packs and/or hot fixes, which may require small updates to the components. No major upgrades are required. Minor configuration changes may be needed and are documented in an Upgrade Guide. Any change in the software must be backward compatible.

The version categories convey the significance of the software changes from one version to another. As the versions are released, you can infer the scope of the changes by its version number. For example:

Figure: Example of a release cycle
Diagram of a release cycle