Release of the nds2 client code proceeds along the following steps. Note that 
all file paths are relative to the top level "client" directory in the svn 
source tree.

 1) Make sure all changes have been listed in ChangeLog and tested

 2) Update the release number in the following places
    * configure.ac:4:AC_INIT([nds2-client],[0.10.5])
    * CMakeLists.txt:28:SET( ${PROJECT_NAME}_MAJOR_VERSION 0 )
      CMakeLists.txt:29:SET( ${PROJECT_NAME}_MINOR_VERSION 10 )
      CMakeLists.txt:30:SET( ${PROJECT_NAME}_PATCH_VERSION 5 )
    Note that non-numeric release numbers should be used only for internal 
    distribution (i.e. testing by group members).

 3) Add entry to debian/changelog (by hand or automated script?)

 4) configure, make, make dist to get the distribution source tarball named e.g.
    nds2-client-0.10.5.tar.gz in the build sirectory.

 5) Run rpmbuild and/or debuild on the tarball. Change and iterate if the 
    build fails (usually problem is a bad spec file or source files not 
    included in the source taball e.g. missing EXTRA_DIST).

 6) commit any changes to svn.

 7) tag the client head version by using a svn copy to e.g.

       https://svn.ligo.caltech.edu/svn/nds2/tags/nds2_client_0_10_5 

 8) upload the tarball to software.ligo.org/lscsoft

 9) announce it to the world (daswg, fan, lscdebian)

10) When the lscsoft package has been tested in the wild. Request to SCCB
    that it be moved to production.

11) Have a Beer

12) Have another beer (All programs need 12 steps)
