Index: openacs-4/packages/acs-core-docs/www/releasing-openacs-core.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/releasing-openacs-core.adp,v diff -u -r1.1.2.10 -r1.1.2.11 --- openacs-4/packages/acs-core-docs/www/releasing-openacs-core.adp 21 Apr 2017 15:07:52 -0000 1.1.2.10 +++ openacs-4/packages/acs-core-docs/www/releasing-openacs-core.adp 2 Jun 2017 11:12:57 -0000 1.1.2.11 @@ -32,7 +32,7 @@ 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 +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 @@ -141,7 +141,7 @@

  • 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
    +things from openacs-4 to OpenACS at the end)

    mkdir /var/tmp/dotlrn-tarball
     cd /var/tmp/dotlrn-tarball
     cvs -d /cvsroot export -r openacs-5-0-0a1 acs-core
     cd /var/tmp/dotlrn-tarball/openacs-4/packages
    @@ -264,8 +264,8 @@
     
     # Clean up after ourselves...
     cd $BASE && rm -rf dotlrn-tarball tarball openacs-4 dotlrn-packages
    -
    ($‌Id: releasing-openacs.xml,v 1.22.2.3 -2016/10/03 09:17:51 gustafn Exp $)
    +
    ($‌Id: releasing-openacs.xml,v 1.22.2.5 +2017/04/22 17:18:48 gustafn Exp $)