| Prev | Chapter�18.�Releasing OpenACS | Next |
|---|
Update Translations.�the section called “How to Update the translations”
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. We generate two changelogs, one for the minor branch and one for the most recent release. The example below is for OpenACS 5.0.2:
cd /var/lib/aolserver/$OPENACS_SERVICE_NAME
+
+OpenACS Core and .LRN Update Translations.�Section�, “How to Update the translations”
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. We generate two changelogs, one for the minor branch and one for the most recent release. The example below is for OpenACS 5.0.2:
cd /var/lib/aolserver/$OPENACS_SERVICE_NAME
cvs2cl -F oacs-5-0 --delta openacs-5-0-0-final:oacs-5-0 -f ChangeLog
cvs2cl -F oacs-5-0 --delta openacs-5-0-1-final:oacs-5-0 -f ChangeLog-recentUpdate Version Numbers.�The version numbers in the documentation and in the packages must be updated. This should only happen after a release candidate is approved.
.LRN: this must be repeated for .LRN modules (dotlrn-core in the dotlrn cvs tree) and for any modified modules in the .LRN prerequisites (dotlrn-prereq in openacs cvs tree). My current working model is that I bulk-update .LRN and OpenACS core but that I don't touch dotlrn-prereq modules - I just use the most recent release and it's up to individual package developers to tag and release those packages when they change. This model is already broken because following it means that dotlrn-prereqs don't get new translations.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
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
+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. Use
+ /var/lib/aolserver/$OPENACS_SERVICE_NAME/packages/acs-core-docs/www/files/update-info.sh
+ with the new version number and the release date as arguments.
+ Run it from /var/lib/aolserver/$OPENACS_SERVICE_NAME/packages:
cd /var/lib/aolserver/$OPENACS_SERVICE_NAME/packages
+ ./acs-core-docs/www/files/update-info 5.2.1 2006-01-16
Install a new site using the modified code and verify that the automated tests pass.
Commit changes to CVS
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
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
@@ -44,7 +30,7 @@
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
+ 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
Make the tarball(s).�
openacs-core.�
Go to a new working space and export the tagged files.
mkdir /var/tmp/tarball
@@ -95,7 +81,7 @@
BASE=/var/tmp/release-$OACS_VERSION
mkdir $BASE
if [ ! -d $BASE ]; then
- echo "Failed creating base dir $BASE"
+ echo "Failed creating base dir $BASE"
exit 1
fi