Release Management

This page describes how we release software.

The following pages might be of use:

  • Development Tree
  • Testing
  • Building a release

    1. Clean the tree by running make checkjunk and adding files as appropriate to the makefiles
    2. Run $PTII/util/testsuite/chkjava on the java files and fix problems
    3. Run $PTII/util/testsuite/jindent on the java files and indent the files to the Ptolemy II coding standard.
    4. Run $PTII/adm/copyright/fixcopyrights (not shipped with the release) and update the copyrights on the .java, .tcl and makefiles
    5. Run the nightly build, build a release and run $PTII/adm/copyright/chkcopyright on all the files.
      find . -type f -print > ~/tmp/ff
      sh ~ptII/adm/copyright/chkcopyright `cat ~/tmp/ff | grep -v .class | grep -v codeDoc | grep -v xml | grep -v alljtests.tcl | grep -v .htm | grep -v qcf | grep -v .dtd | grep -v gif`
      
    6. Tag the tree as the release tree and create a branch For more information about CVS, see the Gigascale CVS Pages

      To make a branch for 4.0-beta, use the following command:

      cd $PTII
      cvs tag -b rel-4-0-beta
      
      Then check out the release branch with
      cd ~/src
      cvs co -r rel-4-0-beta ptII
      mv ptII ptII4.0-beta
      
    7. The nightly build uses a makefile in ~ptII/adm (not shipped) to build the release. Copy the most recent makefile and set up a new tree for the release tree.

    Last Updated: $Date: 2004/06/18 00:12:09 $