Globus Toolkit Versioning

The Globus Toolkit versioning scheme is similar to the approach used for the Linux kernel prior to 3.0. Distributions of the Globus Toolkit are tagged with a version number consisting of three parts:


The major release number represents the major state of the Globus Toolkit. It is incremented when significant architectural shifts occur in toolkit development.

A change in the minor release number indicates that many new features have been added to the Globus Toolkit since the last release. API changes and binary incompatibility may occur between minor releases.

The point release number changes when components of the Globus Toolkit have been updated. Public interfaces may be added but not removed between point releases of the stable release version. Point releases are made to make it easier to update an installation when using source packages and to provide a consistent set of documentation for a collection of package versions.

An installation can be upgraded to a new point release via native packages with the expectation that all services and libraries should continue to work as before, unless new features are enabled.

In addition, release candidates are occasionally made available prior to a public release, to encourage widespread testing. These versions are numbered as above, but with an rcversion suffix, e.g. 5.2.2rc1.

Stable and Development Releases

There are two series in the Globus Toolkit release stream: stable and development. Stable distributions have an even minor version number, while development distributions have an odd minor version number. For example:

Stable Releases Development Releases
globus-4.0.1 globus-3.9.5
globus-4.0.0 globus-3.9.4
globus-3.2.1 globus-3.3.0

Releases in the development series are used to publish new features in a timely manner. Development distributions may behave in unpredictable ways and should not be used in production settings. Unlike stable releases, there is no guarantee of binary compatibility between point versions of development versions.

Package Repositories

Starting with GT 5.2, the Globus Toolkit is provided as a set of native binary package for a number of linux-based platforms. These packages are extensively tested by the Globus Toolkit team and provide a convenient way to install the Globus Toolkit software.

For the GT 5.2 releases, there is a stable repository and a testing repository. The stable repository includes all packages in the latest 5.2 point release, as well as all update packages available from the update packages page. This repository is rooted at the stable repository page, with subdirectories for each supported platform.

The testing repository contains the above packages, plus new versions of packages that have not been as thoroughly tested and documented, or published as updates. The testing repository is rooted at the testing repository page.

Support Commitment

The Globus Alliance offers support for the last two stable minor releases. Support is provided on a best effort basis.

A development release does not receive the same level of support from the Globus Alliance as a stable release. For a development release, new features are given priority over bug fixes.

Releases that are no longer supported by the Globus Alliance remain available in the FTP archive.