Warning: This document describes an old release. Check here for the current version.
Making releases
Main tarballs (#)
Cutting a new release is mostly automated but there are still manual steps that must be taken.
-
Test from a clean CVS checkout.
-
Tag CVS with final tag, convention is now "nimbus-TP2_1", "nimbus-TP2_2", etc.
- $ cd vm/bin/lib/gt4.0/dist
- Edit the version number in this file: $ emacs/vi/nano build.properties
- $ ant create-dist
- $ scp -r result/* [email protected]:/www/workspace.globus.org/downloads/
A number of documentation tasks must be completed, see this section for information about those.
Cloud client (#)
Most cloud client releases do not need to happen in tandem with a service release because the protocol rarely changes.
Making a new cloud client release involves getting the "workspace/vm/cloud-client" tarball builder and reading its README.txt.
The cloud client has its own CHANGES.txt and README.txt files that need updating.
Transfer the final result to the usual place, "[email protected]:/www/workspace.globus.org/downloads/"
It's a good thing to help out and note on the download page which version of the cloud client is actually compatible with various clouds. Especially if there are no clouds that a new version is compatible with, this can happen right after a release of the service and cloud client.
Context broker and agent (#)
The context agent and broker are released more "manually", there is no release generation script they are just tarballs of your efforts. It's a good thing to remove the CVS directories.
