Index: openacs-4/packages/acs-core-docs/www/tutorial-upgrades.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/tutorial-upgrades.adp,v diff -u -r1.4.2.4 -r1.4.2.5 --- openacs-4/packages/acs-core-docs/www/tutorial-upgrades.adp 27 Apr 2022 16:52:20 -0000 1.4.2.4 +++ openacs-4/packages/acs-core-docs/www/tutorial-upgrades.adp 13 Jul 2023 12:43:23 -0000 1.4.2.5 @@ -1,11 +1,11 @@ -{/doc/acs-core-docs {ACS Core Documentation}} {Distributing upgrades of your package} +{/doc/acs-core-docs/ {ACS Core Documentation}} {Distributing upgrades of your package} Distributing upgrades of your package

@@ -20,12 +20,13 @@ release a new version of your package.

For the sake of this example, let's assume you are the package owner of the notes package. It is currently at version 1.5, and you are planning on -releasing version 1.6. It is also located in OpenACS's CVS.

To release your package:

cd /path/to/notes
+releasing version 1.6. It is also located in OpenACS's CVS.

To release your package:

+cd /path/to/notes
 cvs commit -m "Update package to version 1.6."
 cvs tag notes-1-6-final
 cvs tag -F openacs-5-1-compat
-

Of course, make sure you write upgrade scripts (the section called “Writing upgrade -scripts”)

+

Of course, make sure you write upgrade scripts (the section called +“Writing upgrade scripts”)