| Prev | Part�III.�For OpenACS Package Developers | Next |
|---|
update the version number in +
Table of Contents
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 @@ -9,27 +9,25 @@ 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
+ 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
+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 +
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, cvs status -v somefile.
cvs tag -b oacs-5-0
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
openacs-core.�
Go to a new working space and export the tagged files.
mkdir /var/tmp/tarball
+Make the tarball
openacs-core.�
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-4 openacsGenerate 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
-dotlrn.�
Go to a new working space and export the tagged +tar cz -f openacs-5.0.0a1.tar.gz openacs-5.0.0a1
dotlrn.�
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
+ 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
@@ -40,10 +38,10 @@
-r dotlrn-2-0-0a1 dotlrn-core
cd /var/tmp/dotlrn-tarball
mv openacs-4 openacs
-
Copy the dotlrn install.xml file, which controls +
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
+ 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
Test the new tarball
Update on the site