Update /var/lib/aolserver/$OPENACS_SERVICE_NAME/packages/acs-core-docs/www/xml/variables.ent with the new version number.

Add new section in /var/lib/aolserver/$OPENACS_SERVICE_NAME/packages/acs-core-docs/www/xml/for-everyone/release-notes.xml

Regenerate all HTML docs

cd /var/lib/aolserver/$OPENACS_SERVICE_NAME/packages/acs-core-docs/www/xml
make

Update /var/lib/aolserver/$OPENACS_SERVICE_NAME/readme.txt with the new version number

Update version number and release date in all of the core packages. Here's a bash/perl script which works but could be made easier to use. (It depends on all of the old versions and dates being identical.) Run it from /var/lib/aolserver/$OPENACS_SERVICE_NAME/packages:

#!/bin/sh
# run this file from ../packages to renumber all .info version numbers

#---------------------------------------------------------------------
# here's what we're looking for
#---------------------------------------------------------------------
#   <version name="5.1.0d1" url="http:blahblah/acs-kernel-5.1.0d1.apm">
#      <provides url="acs-kernel" version="5.1.0d1"/>
#---------------------------------------------------------------------
# here's what we don't want to touch
#---------------------------------------------------------------------
#      <requires url="acs-kernel" version="5.0.0b4"/>
#---------------------------------------------------------------------

for dir in `find -name *.info`
  do
  perl -p -i -e 's/name="5\.0\.0"/name="5\.1\.0d1"/' $dir
  perl -p -i -e 's/-5\.0\.0.apm"/-5\.1\.0d1.apm"/' $dir
  perl -p -i -e 's/(provides.*version)="5\.0\.0"/\1="5\.1\.0d1"/' $dir
  perl -p -i -e 's/2004-10-21/2004-11-26/' $dir
done

Install a new site using the modified code and verify that the automated tests pass.

Commit changes to CVS

Check out OpenACS Core. The files must be checked out through a cvs account with write access and should be a checkout from the release branch. In this example, we are assuming this is being done as a local user on openacs.org (which make the checkout and tagging operations much faster).

cd /var/tmp
cvs -d /cvsroot checkout -r oacs-5-0 acs-core

If doing .LRN, repeat with the dotlrn cvs tree.

cd /var/tmp
mkdir dotlrn-packages
cd dotlrn-packages
cvs -d /dotlrn-cvsroot checkout -r dotlrn-2-0 dotlrn-all

Tag the tree. If it's a final release of core, move or create the appropriate openacs-major-minor-compat tag. (Ie, if releasing 5.0.3 final, move the openacs-5-0-compat flag.)

cd /var/tmp/openacs-4
cvs tag -F openacs-5-0-0a1
cvs tag -F openacs-5-0-compat

cvs tag -b oacs-5-0

If doing .LRN: Since the .LRN packages aren't all in one module, we iterate through all of the modules. Log in first (cvs login) so that you don't have to log in for each module.

cd /var/tmp/dotlrn-packages
for dir in *; do ( cd $dir && cvs tag dotlrn-2-0-2-final ); done
for dir in *; do ( cd $dir && cvs tag -F openacs-5-0-compat ); done

Note that for the compat tag we use the -F flag which will force the tag to the new version (just in case someone has created the tag already on another version). Excercise care when doing this since you don't want to inadvertently move a prior release tag. Also if the tagging goes horribly wrong for some reason you can delete the tag via "cvs tag -d <symbolic_tag>".

Apply the final tag across the tree. First, check out the entire OpenACS tree, getting the most recent stable version of each package. This is most simply done on openacs.org:

cd /var/tmp
cvs -d /cvsroot checkout -r openacs-5-1-compat openacs-4
cd openacs-4
cvs tag openacs-5-1-2-final