%myvars; ]> update the version number in packages/acs-core-docs/www/xml/variables.ent, readme.txt, and all core .info files. Regenerate the html documentation and commit all the changes. Update the information in the packages/acs-core-docs/www/xml/for-everyone/release-notes.xml file. Check out the whole cvs tree. 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, the cvs user on openacs.org is implied from the ssh login information previously set up. It could be overridden via foobar@openacs.org. cd /var/tmp cvs -d /cvsroot checkout -r oacs-5-0 openacs-4 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. cd /var/tmp/openacs-4 cvs tag -F openacs-5-0-0a1 Tag dotLRN. Since the dotLRN 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 -F dotlrn-2-0-0a1 ); done Make the tarball Go to a new working space and export the tagged files. mkdir /var/tmp/tarball cd /var/tmp/tarball cvs -d :pserver:anonymous@openacs.org:/cvsroot export -r openacs-5-0-0a1 acs-core mv openacs-4 openacs Generate the tarball cd /var/tmp/tarball mv openacs openacs-5.0.0a1 tar cz -f openacs-5.0.0a1.tar.gz openacs-5.0.0a1 Go to a new working space and export the tagged files. (was getting errors here trying to use -d, so gave up and just moved things from openacs-4 to openacs at the end) mkdir /var/tmp/dotlrn-tarball cd /var/tmp/dotlrn-tarball cvs -d :pserver:anonymous@openacs.org:/cvsroot export \ -r openacs-5-0-0a1 acs-core cd /var/tmp/dotlrn-tarball/openacs-4/packages cvs -d :pserver:anonymous@openacs.org:/cvsroot export \ -r openacs-5-0-0a1 dotlrn-prereq cvs -d :pserver:anonymous@dotlrn.openacs.org:/dotlrn-cvsroot export \ -r dotlrn-2-0-0a1 dotlrn-core cd /var/tmp/dotlrn-tarball mv openacs-4 openacs Copy the dotlrn install.xml file, which controls which packages are installed on setup, to the root location: cp /var/tmp/dotlrn-tarball/openacs/packages/dotlrn/install.xml /var/tmp/dotlrn-tarball/openacs Generate the tarball cd /var/tmp/tarball mv openacs dotlrn-2.0.0a1 tar cz -f dotlrn-2.0.0a1.tar.gz dotlrn-2.0.0a1 Test the new tarball Update on the site Setup a local OpenACS server. Edit the file packages/acs-admin/www/build-repository.tcl; Change the line with 'set head_channel' to '5-1' if the version on HEAD in the openacs.org cvs repository is 5.1. Etcetera. You may also want to change the line setting the variable 'repository_dir'. Request /acs-admin/apm/build-repository on your new server. The page will find all branches in the cvs repository labeled oacs-x-y, and build a repository channel for each of those branches where x>=5 (so not for 4.6 and earlier). Finally, it'll build another channel for HEAD, which will be named after what you set in 'head_channel' above. For each channel, it'll do an anonymous checkout of packges and contrib/packages, then build .apm files for each package in the checkout. The files will be stored on the server's hard drive in the directory specified by the 'repository_dir' variable in the page script, by default "[acs_root_dir]/www/repository/". If you're on openacs.org, everything should now be fine. Otherwise, you need to move the entire directory tree to openacs.org:/web/openacs/www/repository, replacing what was already there.