Software release numbering

The values in a software release version convey the significance of the software changes from one version to another. With each version release, you can infer the scope of change by the version number.

There are three main categories of software versions, which are tracked in the version number for a given release, written as major.minor.build number.

Figure: Sample release cycle
Diagram of a release cycle

1: Major

Indicates there are significant changes in the functionality or its components that require an important upgrade of the deployment. Changes that qualify include:

  • Major upgrades of the underlying framework, such as Java or Eclipse
  • Removal of an operating system that is no longer supported
  • Major update of the IXIA TEXTML Server version.
Important: This release type can introduce changes that are not compatible with the configuration of an older version. In this case, MadCap Software provides you with an upgrade procedure.

2: Minor

Introduces new important features, so may require configuration changes and component upgrades.

Important: This release type can introduce changes that are not compatible with the configuration of an older version. In this case, MadCap Software provides you with an upgrade procedure.

3: Build number

Introduces bug fixes through service packs or hot fixes, which may require small updates to the components.

Note: No major upgrades are required. You may need to make minor configuration changes, which are documented in the related Upgrade Guide. Any change in the software must be backward compatible.