-Update Translations. the section called -“How to Update the -translations” +Update Translations. the section called “How to Update +the translations”
Rebuild the Changelog. Rebuild the
@@ -27,10 +26,9 @@
cvs2cl -F oacs-5-0
--delta openacs-5-0-1-final
:oacs-5-0
-f ChangeLog-recent
-Update 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 +Update 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 @@ -46,8 +44,7 @@ /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 -+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 @@ -63,8 +60,8 @@
-Tag the files in CVS. The steps to -this point should have ensured that the head of the current branch +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.
cvs status -v
-somefile
.-cvs tag -boacs-5-0
+somefile.cvs tag -boacs-5-0
If doing .LRN: Since the .LRN packages aren't all in one module, we iterate through all of the modules. Log in first (cvs @@ -164,27 +160,25 @@
-Test the new tarball(s). Download -the tarballs just created and install them and make sure everything +Test the new tarball(s). Download the +tarballs just created and install them and make sure everything looks okay and that automated tests pass.
-Update Web site. Update the -different places on OpenACS.org where we track status.
Release Status for the current version - something like http://openacs.org/projects/openacs/5.0/milestones
Home page of openacs.org
Post a new news item
-Clean Up. Clean up after -yourself.
cd /var/tmp
+Clean Up. Clean up after yourself.cd /var/tmp
rm -rf tarball dotlrn-tarball dotlrn-packages openacs-5.0.0a1
rm -rf /var/tmp/openacs-4
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).
-#!/bin/bash +detailed above until the process is stabilized).#!/bin/bash # if TAG=1 create the cvs tags otherwise assume they exist. TAG=1 @@ -245,7 +239,7 @@ mkdir tarball cd tarball cvs -d $OACS_CVSROOT export -r openacs-$OACS_VERSION acs-core -mv openacs-4 openacs-${OACS_VERSION//-/.} +mv opeancs-4 openacs-${OACS_VERSION//-/.} tar -czf ../openacs-${OACS_VERSION//-/.}.tar.gz openacs-${OACS_VERSION//-/.} cd .. @@ -265,14 +259,14 @@ # Clean up after ourselves... cd $BASE && rm -rf dotlrn-tarball tarball openacs-4 dotlrn-packages -($Id: releasing-openacs.xml,v 1.23 -2017/08/07 23:47:54 gustafn Exp $)
+
($Id: releasing-openacs.xml,v 1.24 +2017/12/24 13:15:07 gustafn Exp $)