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.3 -r1.4 --- openacs-4/packages/acs-core-docs/www/tutorial-upgrades.adp 8 Nov 2017 09:42:12 -0000 1.3 +++ openacs-4/packages/acs-core-docs/www/tutorial-upgrades.adp 25 Apr 2018 08:38:28 -0000 1.4 @@ -3,11 +3,11 @@ Distributing upgrades of your package -
+ leftLink="tutorial-distribute" leftLabel="Prev" + title="Chapter 10. Advanced +Topics" + rightLink="tutorial-notifications" rightLabel="Next"> +

Distributing upgrades of your package

<authorblurb>

by Jade Rubick

</authorblurb>

The OpenACS Package Repository builds a list of packages that @@ -17,18 +17,17 @@ 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”)

- \ No newline at end of file + rightLink="tutorial-notifications" rightLabel="Next" rightTitle="Notifications" + homeLink="index" homeLabel="Home" + upLink="tutorial-advanced" upLabel="Up"> + \ No newline at end of file