Index: openacs-4/packages/acs-core-docs/www/xml/releasing-openacs.xml
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/releasing-openacs.xml,v
diff -u -r1.5.2.3 -r1.5.2.4
--- openacs-4/packages/acs-core-docs/www/xml/releasing-openacs.xml 9 Dec 2003 09:55:14 -0000 1.5.2.3
+++ openacs-4/packages/acs-core-docs/www/xml/releasing-openacs.xml 11 Dec 2003 13:54:40 -0000 1.5.2.4
@@ -21,11 +21,10 @@
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.
+ 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 openacs-4
@@ -41,7 +40,16 @@
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.
+ Note that 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>".
+
+ 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
@@ -59,14 +67,13 @@
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
+cvs -d /cvsroot export -r openacs-5-0-0a1 acs-core
- Generate the tarball
+ Generate the tarball.
cd /var/tmp/tarball
-mv openacs openacs-5.0.0a1
+mv openacs-4 openacs-5.0.0a1
tar cz -f openacs-5.0.0a1.tar.gz openacs-5.0.0a1
@@ -85,30 +92,26 @@
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
+cvs -d /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
+cvs -d /cvsroot export -r openacs-5-0-0a1 dotlrn-prereq
+cvs -d /dotlrn-cvsroot export -r dotlrn-2-0-0a1 dotlrn-core
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
+ cp /var/tmp/dotlrn-tarball/openacs-4/packages/dotlrn/install.xml \
+ /var/tmp/dotlrn-tarball/openacs-4
Generate the tarball
- cd /var/tmp/tarball
-mv openacs dotlrn-2.0.0a1
+ cd /var/tmp/dotlrn-tarball
+mv openacs-4 dotlrn-2.0.0a1
tar cz -f dotlrn-2.0.0a1.tar.gz dotlrn-2.0.0a1
@@ -120,7 +123,18 @@
Test the new tarball
- Update on the site
+ Update openacs.org frontpage, bug-tracker versions, project page, etc.
+
+ Clean up after yourself.
+ cd /var/tmp
+rm -rf tarball dotlrn-tarball dotlrn-packages openacs-5.0.0a1
+
+
+ Here is a shell script that automates this whole process...
+
+
+ release script missing
+