= Constructing a release for CMT =


== External dependencies ==

Doxygen

html2ps


== Final step on the sources ==

The final step for preparing the release consists in 

Files to be changed lastly are:
 1. cmt_version.h
 1. CMTDoc.xml
 1. requirements (only when major release changes)

Sequence is:

 1. Changing CMTDoc.xml (and requirements if needed) in HEAD
 1. svn copy to new tag
 1. 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          || lxplus.cern.ch  ||
||SunOS-sun4u         || ccasn.in2p3.fr  ||
||AIX-002064874C00    || ccars.in2p3.fr  ||

== 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
}}}
 1. Prepare !ReleaseNotes.html form !ChangeLog
 1. Prepare ../doc/download.html by installing the reference to the new version. This file is stored in the svn cmtsite repository.


== 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*
}}}

== Export binaries at CERN ==

The CMT binaries at cern are in the /afs/cern.ch/sw/contrib/CMT/ directory.
For changing the disk quota, you should contact the administrators: renshal, alibrari (  
see http://consult.cern.ch/qa/1381).


== Final SVN tagging ==