A major Bright Cluster Manager release has a major number associated with it. For example:
5 (same as 5.0), or 6 (same as 6.0).
A minor release has a number after the decimal point. For example:
5.1, or Bright 6.1
A particular minor version can be updated regularly via YUM/zypper within the same minor version.
Upgrades to the next minor version are possible by following appropriate recipes, for upgrades that occur between minor releases of the same major release. For example:
5 to 5.1, or 5.1 to 5.2, or 6.0 to 6.1
But not: 5.2 to 6.0
To upgrade between major versions 5.x to 6.x is not possible. Upgrading from 6.0 or 6.1 to 7.0 is possible with the procedure described in /faq/index.php?action=artikel&cat=2&id=173.
A subminor number-tagged release is a release with a number tagged on after a hyphen. This becomes available after a sufficient changes have been made in the packages of a minor release. This usually happens every two or three weeks at present. The numbering leads to releases tagged, for example as follows for the 6.0 release:
6.0-1, or 6.0-2 .... or 6.0-21, or 6.0-22.
Subminor number-tagged release names are not used as official Bright release names. The official release naming scheme remains the the major release or minor release as the version name. Subminor number-tagged releases are labels of convenience for snapshots of the current production release, and includes cluster manager packages that have gone through QA. A subminor release is therefore basically like patch level releases. Subminor number-tagged releases are only released as DVDISOs for download, and are not kept available for download for long. Only the latest of the subminor number-tagged releases is available for download at any time. Internally, the version of many packages used at any time can move on several times between subminor number-tagged releases outside of the QA process for 3rd party or distribution packages. Thus, a cluster that is updated via YUM/zypper does not jump from subminor number-tagged release to subminor number-tagged release, but instead transitions gradually between the packages that are updated from the various repositories during normal administration, and matches the number-tagged release snapshots at times.
It's not an officially supported method, but the version number of an ISO release can be revealed like this:
Mount the iso and list the data/cm-rpms directory:
mount -o loop /path/to/bright.iso /mnt
One of the sub-directories will have a name similar to :
Here, 15 is the subminor release number.