Constructing a release for CMT

Final step on the sources

The final step for preparing the release consists in

Files to be changed lastly are:

1. cmt_version.h
2. CMTDoc.xml
3. requirements (only when major release changes)

Sequence is:

1. Changing CMTDoc.xml (and requirements if needed) in HEAD
2. svn copy to new tag
3. Changing cmt_version.h in new tag only (stays "HEAD" in HEAD)

Build the binaries

Binaries are built on various machines, then copied to /lal/CMT/*/

VisualC	laptop
CYGWIN_NT-5.1-i686	laptop

OSF1-alpha	asc
Linux-i686	lxbuild002
Linux-x86_64	atlas2.lal.in2p3
SunOS-sun4u	ccasn.in2p3.fr
AIX-002064874C00	ccars.in2p3.fr

• Check that once copied to LAL, all cmt.exe are executable
• Remove *.o files before creating the tar balls
• Create the symlinks cmt -> cmt.exe

Build the documentations

1. Run the documentation generators

   gmake doxygen       # on atlas.lal.in2p3.fr
   gmake gendoc        # needs Python >= 2.3
   gmake pdf           # on lxplus
   

2. Prepare ReleaseNotes.html form ChangeLog
3. Prepare ../doc/download.html by installing the reference to the new version.

Build the pacman kit

gmake pacman
cp CMT-<version>.pacman /www/Web/htdocs/cmtsite/pacman/cache

Export to the CMT Web site

gmake Export        on a LAL machine
cd ../../
rm CMT*

Final SVN tagging