How to create release notes for gLite 3.1 release series
Create new repository
Create repository at the following location:
/afs/cern/ch/project/gd/www/glite/prepare/prod/3.1
http://grid-deployment.web.cern.ch/grid-deployment/glite/prepare/prod/3.1
Details to create the repository can be found
here.
Extract Savannah information
Export
Savannah patch information for the patches supposed to be released.
Install SL Virtual machine
- Install via vNode portal a fresh and clean SL machine.
- Setup CVS:
export CVSROOT=:pserver:anonymous@glite.cvs.cern.ch:/cvs/glite
export CVS_RSH=ssh
|
- Download release tools from CVS
cvs co org.glite.integration.release
cd org.glite.integration.release
|
- AND/OR, in case of release to x86_64, download release tools for x86_64 from CVS
cvs co org.glite.integration.release
cd org.glite.integration.release/x86_64
|
- Download patch file (see above) from Savannah.
Note : To create the release notes for 64Bit, you have to change into
org.glite.integration.release/x86_64
Create release notes
Make sure to install openldap-servers before launching the release notes creation, since yum doesn't recognize the openldap package installed by the dag repository, via:
yum install openldap-servers
|
Create the release notes via:
createReleasePages.sh --date= --gliteRelease=3.1 --update= --patchFile= --priority= |
The script will attempt to install the target listed in
lists/metapackages.R3.1.list and extract (from yum) the list of rpms which are neccessary for this metapackage. After this, it downloads the current list from the glite web server ( e.g.
http://glite.web.cern.ch/glite/packages/R3.1/deployment/glite-VOBOX/3.1.9-0/glite-VOBOX-3.1.9-0.rpm.list.txt) and compares the two lists. If a difference is found the metapackage is marked on the main page (
packages/R3.1/deployment/default.asp).
Note: In case a new metapackage needs to be released, be sure to have it listed in
lists/metapackages.R3.1.list and to have a new directory in
glite/packages/R3.1/deployment/ created.
As we have seen lot of error during the rpms list creation a new script is available only for this task.
./rpm_list_creation/create_list_rpms.sh -d repo_files_url -n type_of_node -r [3.2|3.1] -a [x86_86|i386]
for exemple
./rpm_list_creation/create_list_rpms.sh -d http://grid-deployment.web.cern.ch/grid-deployment/glite/repos/3.2/ -n glite-WN -r 3.2 -a x86_86
This command will create the rpm list (html and txt) in the folder /tmp/ then copy them in /mnt/glite_repository/packages/R${release}/${platform}/deployment/${nodetype}/${nodeversion}/
with he suffix _new.
Upload release notes
Upload release notes to the gLite Webserver with
./scripts/uploadReleaseNotes.sh |
Edit release notes
Edit/beautify the release notes section as they are added in raw format. Either in the exported xml (recommended) or with an html editor and mounted network drive.
Linux:
| SL4 |
mount -t smbfs -o username=CERN\\$MYUSER //glite.web.cern.ch/glite /mnt/glite_repository |
| SL5 |
mount -t cifs -o username=CERN\\$MYUSER //glite.web.cern.ch/glite /mnt/glite_repository |
Activate the new pages
cd /mnt/glite/glite_repository/packages/R.3/
./publishRelease.sh |
--
FelixNikolausEhm - 17 Nov 2008
Copyright &© by the contributing authors. All material on this collaboration platform is the property of the contributing authors.