Releasing the Globus Toolkit

Releasing a 4.0.x candidate

Step one is to announce the code freeze to gt-dev@globus.org.

Ideally you will be able to grab a source installer and binaries from the nightly builds at the NMI Build&Test pool. However, here's what's happening up there, and how you could do it manually:

export CVSROOT=:pserver:anonymous@cvs.globus.org:/home/globdev/CVS/globus-packages
cvs co -r globus_4_0_branch packaging
cd packaging
fait_accompli/installer.sh
tar czf gt4.0.x-all-source-installer.tar.gz gt4.0.x-all-source-installer
sha1sum gt*installer.tar.gz

After building the source, you can create binaries via the following command:

fait_accompli/bundle-binaries $GLOBUS_LOCATION

The binaries will land in a subdir called "tmp", and should be renamed to reflect the architecture the binaries were built on.

Releasing 4.0.x (and 4.2.x)

In addition to the above, you will need to do the following:

Get updated contribs from contributors and put them in a contrib/ subdirectory in the installers
Update the version returned by globus-version by editing common/source/programs/globus-version.in (Mike Link)
Update the version numbers in packaging/fait_accompli/{installer.configure.in,binary.configure.in}
Update the version in the build.xml buildfile under wsrf/java (as of this writing typically done by Rachana)
Update the version returned by MDS providers, ServiceMetaDataResourceProperty and the GRAM provider (as of this writing, typically done by Laura Pearlman)
Send email requesting a tag the release with globus_4_0_x. The packager is responsible for tagging packaging/, autotools/, test/, and tarfiles/
Send email requesting a 4.0.x version in bugzilla.
Work with the doc coordinator to get new docs and API docs.
Change the $releasenotes trigger in alliance-web/CVSROOT/website.pl
Update packaging/make-packages.pl to use the globus_4_0_x tag

Add the release to the gtsurvey database on yeah.mcs.anl.gov by adding a new release ID to the release table, then adding the download files to the software table. Verify that they show up at the survey page at http://www-unix.globus.org/toolkit/survey/index.php

Here's an example of adding files for the 4.0.3 release:

gtsurvey=> INSERT INTO release(release_name) VALUES('4.0.3');
INSERT 91694629 1
gtsurvey=> SELECT release_id FROM release WHERE release_name='4.0.3';
release_id
------------
	18
(1 row)

gtsurvey=> INSERT INTO software(release_id, software_filename,
software_url_base) VALUES (18, 'gt4.0.3-x86_rhas_4-installer.tar.gz',
'http://www-unix.globus.org/ftppub/gt4/4.0/4.0.3/installers/bin/');
INSERT 91700640 1

Create a page for the 4.0.x downloads at http://www.globus.org/toolkit/downloads/4.0.x/ by updating the website CVS at cvs.globus.org:/home/globdev/CVS/alliance-web in module alliance/toolkit/downloads
Also update the main downloads/index.html to refer to 4.0.x as the preferred download.
Make the files available at ftp.globus.org:/disks/ftp.globus.org/pub/gt4/4.0/4.0.x/installers/{src,bin}
Besides the installers, you will need to make the GPT (in packaging/fait_accompli) and contribs available. Finally, make the ws-core only release by running "ant distsrc" and "ant distbin" in wsrf/.
Update toolkit/survey/wherenow.php to include links to the new release notes.
Add a new entry to the version_dir in advisories.html for the new release.
Update the toolkit/docs/latest-stable and toolkit/downloads/latest-stable symlinks on cvs.globus.org

Finally, send an announcement to announce@globus.org, and unfreeze CVS with an announce to gt-dev@globus.org.

Releasing a 3.2 candidate

setenv CVSROOT cvs.globus.org:/home/globdev/CVS/gridservices
cvs co -r globus_3_2_branch packaging
edit fait_accompli/all-release.sh to use rcN in the name
fait_accompli/all-release.sh
cd source-trees/ogsa-cvs
cvs tag globus_3_2_rcN
cd ../gt2-cvs
cvs -d cvs.globus.org:/home/globdev/CVS/globus-packages tag globus_3_2_rcN
cd ../.. (the packaging/ directory)
cvs tag globus_3_2_rcN (packaging is not part of the ogsa-cvs checkout)
tar czf gt3.2rcN-all-installer.tar.gz gt3.2rcN-all-installer
md5sum gt3.2rcN-all-installer.tar.gz
Put on website somewhere, send mail to gt3-dev-int
If doing release.sh and preogsi-release.sh, rm -fr *-output, iterate.
GT3 core source: ./make-packages -n --packages=core. The result will be in package-output/core-0.6.tar.gz

Releasing 3.2

As above, except also copy the contrib/ directory to your packaging/ location (Available from http://www-unix.mcs.anl.gov/~bacon/3.2/contrib.tar.gz)
The CVS tag will be globus_3_2_0
Edit the installers to use globus_3_2_0, not globus_3_2_branch
Run release.sh and preogsi-release.sh in addition to all-release.sh
That concludes the source installers. All the rest of the instructions are for binaries
Copy the installers and fait_accompli/*.xml to:
- evitable (fedora1)
- atlantis (solaris9)
- nmi-sles8-ia64.cs.wisc.edu (sles8/IA64)
- mayed (rh7.3)
Run install-gt3 && install-gt3-mmjfs for the all/base installers
Then set GPT_LOCATION and GLOBUS_LOCATION to the install dir
Run $GPT_LOCATION/sbin/gpt-bundle -xml=TYPE-3.2.gpt-bundle.xml -nodeps to generate the binary GPT bundle. Note: The IA64 needs a custom version, since it uses a different flavor than the others. s/gcc32/gcc64/ in the .xml files.
Create a directory for the binary containing the following from the source installers (Available from http://www-unix.mcs.anl.gov/~bacon/3.2/blank.tar.gz):
- contrib/
- gpt-3.0.1-src.tar.gz
- schedulers
- and install-gt3-bin from packaging/fait_accompli
Add the generated binary bundle, and replace the BUNDLE_NAME in install-gt3-bin
Create a .tar.gz of it, md5sum, publish.
GT3 core binary: Untar core-0.6.tar.gz, run ant dist. Create a tarfile and zipfile of the build/ogsa-3.2 directory.

The FTP Site

The structure from ftp://ftp.globus.org/pub/gt3/3.2/beta can be used.

On an MCS machine, you can access it as /mcs/ftp.globus.org on the filesystem