Index: openacs-4/packages/acs-core-docs/www/releasing-openacs.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/releasing-openacs.html,v diff -u -r1.6.2.1 -r1.6.2.2 --- openacs-4/packages/acs-core-docs/www/releasing-openacs.html 21 Nov 2003 11:14:09 -0000 1.6.2.1 +++ openacs-4/packages/acs-core-docs/www/releasing-openacs.html 8 Dec 2003 15:41:18 -0000 1.6.2.2 @@ -1,4 +1,6 @@ -Appendix�E.�How to package and release OpenACS
Alex logo
Prev Part�III.�For OpenACS Package Developers Next

Appendix�E.�How to package and release OpenACS

  1. Check out the cvs tree. The files must be checked out +Appendix�E.�How to package and release OpenACS

    Alex logo
    Prev Part�III.�For OpenACS Package Developers Next

    Appendix�E.�How to package and release OpenACS

    1. 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. +

    2. Check out the cvs tree. The files must be checked out through a cvs account with write access. 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. 

      @@ -46,4 +48,4 @@

    3. Generate the tarball

      
 cd /tmp/tarball
 tar cz -f dotlrn-2.0.0a1.tar.gz openacs
-

  • Test the new tarball

  • Update on the site

    • Prev Home Next
    Add the Service to CVS - OPTIONAL Up Part�IV.�For OpenACS Platform Developers
    docs@openacs.org
    View comments on this page at openacs.org
    +

  • Test the new tarball

  • Update on the site

    • Prev Home Next
    Appendix�D.�Using CVS with an OpenACS Site Up Part�IV.�For OpenACS Platform Developers
    docs@openacs.org
    View comments on this page at openacs.org