Index: openacs-4/packages/acs-core-docs/www/releasing-openacs-core.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/releasing-openacs-core.html,v diff -u -r1.2.2.6 -r1.2.2.7 --- openacs-4/packages/acs-core-docs/www/releasing-openacs-core.html 8 Nov 2004 19:59:34 -0000 1.2.2.6 +++ openacs-4/packages/acs-core-docs/www/releasing-openacs-core.html 24 Nov 2004 04:29:18 -0000 1.2.2.7 @@ -20,7 +20,7 @@ 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 -done
Commit changes to CVS
Rubuild the Changelog.�Rebuild the Changelog. I use a tool called cvs2cl. Run this command from the package root to automatically generate a Changelog file in the same dir:
cd /var/lib/aolserver/$OPENACS_SERVICE_NAME +done
Commit changes to CVS
Rebuild the Changelog.�Rebuild the Changelog. I use a tool called cvs2cl. Run this command from the package root to automatically generate a Changelog file in the same dir:
cd /var/lib/aolserver/$OPENACS_SERVICE_NAME perl /var/tmp/cvs2cl/cvs2cl.pl -F oacs-5-0 --delta openacs-5-0-0-final:oacs-5-0
Commit changes
Tag the files in CVS.�The steps to this point should have ensured that the head of the current branch contains the full set of code to release. Now we need to tag it as the code to be released.
Check out OpenACS Core. The files must be checked
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.16.2.3 -r1.16.2.4
--- openacs-4/packages/acs-core-docs/www/xml/releasing-openacs.xml 8 Nov 2004 19:59:41 -0000 1.16.2.3
+++ openacs-4/packages/acs-core-docs/www/xml/releasing-openacs.xml 24 Nov 2004 04:28:59 -0000 1.16.2.4
@@ -70,7 +70,7 @@