<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>OpenACS Core and .LRN</title><meta name="generator" content="DocBook XSL Stylesheets V1.60.1"><link rel="home" href="index.html" title="OpenACS Core Documentation"><link rel="up" href="releasing-openacs.html" title="Chapter�18.�Releasing OpenACS"><link rel="previous" href="releasing-openacs.html" title="Chapter�18.�Releasing OpenACS"><link rel="next" href="update-repository.html" title="How to Update the OpenACS.org repository"><link rel="stylesheet" href="openacs.css" type="text/css"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><a href="http://openacs.org"><img src="/doc/images/alex.jpg" border="0" alt="Alex logo"></a><table width="100%" summary="Navigation header" border="0"><tr><td width="20%" align="left"><a accesskey="p" href="releasing-openacs.html">Prev</a> </td><th width="60%" align="center">Chapter�18.�Releasing OpenACS</th><td width="20%" align="right"> <a accesskey="n" href="update-repository.html">Next</a></td></tr></table><hr></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="releasing-openacs-core"></a>OpenACS Core and .LRN</h2></div></div><div></div></div><div class="orderedlist"><ol type="1"><li><p><b>Update Translations.�</b><a href="update-translations.html" title="How to Update the translations">Section�, “How to Update the translations”</a></p></li><li><p><b>Rebuild the Changelog.�</b>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:</p><pre class="screen"><span class="action"><span class="action">cd /var/lib/aolserver/$OPENACS_SERVICE_NAME
cvs2cl -F <span class="replaceable"><span class="replaceable">oacs-5-0</span></span> --delta <span class="replaceable"><span class="replaceable">openacs-5-0-0-final</span></span>:<span class="replaceable"><span class="replaceable">oacs-5-0</span></span> -f ChangeLog
cvs2cl -F <span class="replaceable"><span class="replaceable">oacs-5-0</span></span> --delta <span class="replaceable"><span class="replaceable">openacs-5-0-1-final</span></span>:<span class="replaceable"><span class="replaceable">oacs-5-0</span></span> -f ChangeLog-recent</span></span></pre></li><li><p><b>Update Version Numbers.�</b>The version numbers in the documentation and in the packages must be updated. This should only happen after a release candidate is approved.</p><i><span class="remark">.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 <a href="releasing-package.html" title="How to package and release an OpenACS Package">release those packages</a> when they change. This model is already broken because following it means that dotlrn-prereqs don't get new translations.</span></i><div class="orderedlist"><ol type="a"><li><p>Update /var/lib/aolserver/$OPENACS_SERVICE_NAME/packages/acs-core-docs/www/xml/variables.ent with the new version number.
</p></li><li><p>Add new section in /var/lib/aolserver/$OPENACS_SERVICE_NAME/packages/acs-core-docs/www/xml/for-everyone/release-notes.xml
</p></li><li><p>Regenerate all HTML docs</p><pre class="screen">cd /var/lib/aolserver/$OPENACS_SERVICE_NAME/packages/acs-core-docs/www/xml
make</pre></li><li><p>Update /var/lib/aolserver/$OPENACS_SERVICE_NAME/readme.txt with the new version number</p></li><li><p>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:</p><pre class="screen">cd /var/lib/aolserver/$OPENACS_SERVICE_NAME/packages
./acs-core-docs/www/files/update-info <span class="replaceable"><span class="replaceable">5.2.1</span></span> <span class="replaceable"><span class="replaceable">2006-01-16</span></span></pre></li><li><p>Install a new site using the modified code and verify that the automated tests pass.</p></li><li><p>Commit changes to CVS</p></li></ol></div></li><li><p><b>Tag the files in CVS.�</b>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.</p><div class="orderedlist"><ol type="a"><li><p>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).</p><pre class="screen"><span class="action"><span class="action">cd /var/tmp
cvs -d /cvsroot checkout -r <span class="replaceable"><span class="replaceable">oacs-5-0</span></span> acs-core</span></span></pre><p>If doing .LRN, repeat with the dotlrn cvs tree.</p><pre class="screen"><span class="action"><span class="action">cd /var/tmp
mkdir dotlrn-packages
cd dotlrn-packages
cvs -d /dotlrn-cvsroot checkout -r <span class="replaceable"><span class="replaceable">dotlrn-2-0</span></span> dotlrn-all
</span></span></pre></li><li><p>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.)</p><pre class="screen"><span class="action"><span class="action">cd /var/tmp/openacs-4
cvs tag -F <span class="replaceable"><span class="replaceable">openacs-5-0-0a1</span></span>
cvs tag -F <span class="replaceable"><span class="replaceable">openacs-5-0-compat</span></span>
</span></span></pre><div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Branching</h3><p>When we feature-freeze on HEAD as part of the release process, we are blocking new development. To avoid this, we branch the code at this point, so that new work can continue on HEAD while the branch is stabilized for release. However, branching means that bug fixes have to be synchronized between HEAD and the branch, and bug fixes tend to be more frequent right at this time. Therefore, our actual branch point is as late as possible - essentially, we do not branch until and unless new feature work is actively blocked by the feature freeze. Branching is almost the same as tagging, except for the flag and slightly different tag nomenclature. To see the list of old branches, <tt class="computeroutput">cvs status -v somefile</tt>.</p><pre class="screen">cvs tag -b <span class="replaceable"><span class="replaceable">oacs-5-0</span></span></pre></div><p>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.</p><pre class="screen"><span class="action"><span class="action">cd /var/tmp/dotlrn-packages
for dir in *; do ( cd $dir && cvs tag <span class="replaceable"><span class="replaceable">dotlrn-2-0-2-final</span></span> ); done
for dir in *; do ( cd $dir && cvs tag -F <span class="replaceable"><span class="replaceable">openacs-5-0-compat</span></span> ); done
</span></span></pre><p>Note that for the compat tag we use the <span class="action"><span class="action">-F</span></span> 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 "<b class="command">cvs tag -d <symbolic_tag></b>".</p></li><li><p>Apply the <tt class="computeroutput">final</tt> 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:</p><pre class="screen"><span class="action"><span class="action">cd /var/tmp
cvs -d /cvsroot checkout -r <span class="replaceable"><span class="replaceable">openacs-5-1-compat</span></span> openacs-4
cd openacs-4
cvs tag <span class="replaceable"><span class="replaceable">openacs-5-1-2-final</span></span></span></span></pre></li></ol></div></li><li><p><b>Make the tarball(s).�</b></p><div class="itemizedlist"><ul type="disc"><li><p><b>openacs-core.�</b></p><div class="orderedlist"><ol type="a"><li><p>Go to a new working space and export the tagged files.</p><pre class="screen"><span class="action"><span class="action">mkdir /var/tmp/tarball
cd /var/tmp/tarball
cvs -d /cvsroot export -r <span class="replaceable"><span class="replaceable">openacs-5-0-0a1</span></span> acs-core</span></span></pre></li><li><p>Generate the tarball.</p><pre class="screen"><span class="action"><span class="action">cd /var/tmp/tarball
mv openacs-4 openacs-<span class="replaceable"><span class="replaceable">5.0.0a1</span></span>
tar cz -f <span class="replaceable"><span class="replaceable">openacs-5.0.0a1.tar.gz</span></span> openacs-<span class="replaceable"><span class="replaceable">5.0.0a1</span></span>
</span></span></pre></li></ol></div></li><li><p><b>dotlrn.�</b></p><div class="orderedlist"><ol type="a"><li><p>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)</p><pre class="screen"><span class="action"><span class="action">mkdir /var/tmp/dotlrn-tarball
cd /var/tmp/dotlrn-tarball
cvs -d /cvsroot export -r <span class="replaceable"><span class="replaceable">openacs-5-0-0a1</span></span> acs-core
cd /var/tmp/dotlrn-tarball/openacs-4/packages
cvs -d /cvsroot export -r <span class="replaceable"><span class="replaceable">openacs-5-0-0a1</span></span> dotlrn-prereq
cvs -d /dotlrn-cvsroot export -r <span class="replaceable"><span class="replaceable">dotlrn-2-0-0a1</span></span> dotlrn-core
</span></span></pre></li><li><p>Copy the dotlrn install.xml file, which controls
which packages are installed on setup, to the root
location:</p><pre class="screen"><span class="action"><span class="action">cp /var/tmp/dotlrn-tarball/openacs-4/packages/dotlrn/install.xml \
/var/tmp/dotlrn-tarball/openacs-4
</span></span></pre></li><li><p>Generate the tarball</p><pre class="screen"><span class="action"><span class="action">cd /var/tmp/dotlrn-tarball
mv openacs-4 dotlrn-<span class="replaceable"><span class="replaceable">2.0.0a1</span></span>
tar cz -f <span class="replaceable"><span class="replaceable">dotlrn-2.0.0a1.tar.gz</span></span> dotlrn-<span class="replaceable"><span class="replaceable">2.0.0a1</span></span>
</span></span></pre></li></ol></div></li></ul></div></li><li><p><b>Test the new tarball(s).�</b>Download the tarballs just created and install them and make sure everything looks okay and that automated tests pass.</p></li><li><p><b>Update Web site.�</b>Update the different places on OpenACS.org where we track status.</p><div class="itemizedlist"><ul type="disc"><li><p>Release Status for the current version - something like http://openacs.org/projects/openacs/5.0/milestones</p></li><li><p>Home page of openacs.org</p></li><li><p>Post a new news item</p></li></ul></div></li><li><p><b>Clean Up.�</b>Clean up after yourself.</p><pre class="screen"><span class="action"><span class="action">cd /var/tmp
rm -rf tarball dotlrn-tarball dotlrn-packages openacs-<span class="replaceable"><span class="replaceable">5.0.0a1</span></span>
rm -rf /var/tmp/openacs-4</span></span></pre></li></ol></div><p>
Here is a shell script that automates packaging the tarball (it's a bit out of date with the new steps - I've been doing everything manually or with little throwaway scripts as detailed above until the process is stabilized).
</p><pre class="programlisting">#!/bin/bash
# if TAG=1 create the cvs tags otherwise assume they exist.
TAG=1
# What release version are we building; version format should be
# dashes rather than dots eg. OACS_VERSION=5-0-0b4
OACS_VERSION=5-0-0b4
DOTLRN_VERSION=2-0-0b4
OACS_BRANCH=oacs-5-0
DOTLRN_BRANCH=dotlrn-2-0
DOTLRN_CVSROOT=/dotlrn-cvsroot
OACS_CVSROOT=/cvsroot
#
# Nothing below here should need to change...
#
BASE=/var/tmp/release-$OACS_VERSION
mkdir $BASE
if [ ! -d $BASE ]; then
echo "Failed creating base dir $BASE"
exit 1
fi
cd $BASE
if [ $TAG -eq 1 ]; then
# Checkout and tag the release
cvs -d $OACS_CVSROOT checkout -r $OACS_BRANCH openacs-4
cd openacs-4
cvs tag -F openacs-$OACS_VERSION
cd ../
# Checkout and tag the dotlrn release
mkdir dotlrn-packages
cd dotlrn-packages
cvs -d $DOTLRN_CVSROOT checkout -r $DOTLRN_BRANCH dotlrn-all
for dir in *; do ( cd $dir && cvs tag -F dotlrn-$DOTLRN_VERSION ); done
cd ../
#
# Should check for .sql .xql .adp .tcl .html .xml executable files and squak if found.
#
fi
# Generate tarballs...
#
# openacs
#
mkdir tarball
cd tarball
cvs -d $OACS_CVSROOT export -r openacs-$OACS_VERSION acs-core
mv opeancs-4 openacs-${OACS_VERSION//-/.}
tar -czf ../openacs-${OACS_VERSION//-/.}.tar.gz openacs-${OACS_VERSION//-/.}
cd ..
# dotlrn
#
mkdir dotlrn-tarball
cd dotlrn-tarball
cvs -d $OACS_CVSROOT export -r openacs-$OACS_VERSION acs-core
cd openacs-4/packages
cvs -d $OACS_CVSROOT export -r openacs-$OACS_VERSION dotlrn-prereq
cvs -d $DOTLRN_CVSROOT export -r dotlrn-$DOTLRN_VERSION dotlrn-core
cd ../..
cp -f openacs-4/packages/dotlrn/install.xml openacs-4
mv openacs-4 dotlrn-${DOTLRN_VERSION//-/.}
tar -czf ../dotlrn-${DOTLRN_VERSION//-/.}.tar.gz dotlrn-${DOTLRN_VERSION//-/.}
# Clean up after ourselves...
cd $BASE && rm -rf dotlrn-tarball tarball openacs-4 dotlrn-packages
</pre><div class="cvstag">($Id: releasing-openacs-core.html,v 1.12 2006/06/04 00:45:24 donb Exp $)</div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="releasing-openacs.html">Prev</a> </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right"> <a accesskey="n" href="update-repository.html">Next</a></td></tr><tr><td width="40%" align="left">Chapter�18.�Releasing OpenACS </td><td width="20%" align="center"><a accesskey="u" href="releasing-openacs.html">Up</a></td><td width="40%" align="right"> How to Update the OpenACS.org repository</td></tr></table><hr><address><a href="mailto:docs@openacs.org">docs@openacs.org</a></address></div><a name="comments"></a><center><a href="http://openacs.org/doc/current/releasing-openacs-core.html#comments">View comments on this page at openacs.org</a></center></body></html>