Index: openacs-4/packages/acs-core-docs/www/eng-standards-versioning.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/eng-standards-versioning.html,v diff -u -r1.8.2.8 -r1.8.2.9 --- openacs-4/packages/acs-core-docs/www/eng-standards-versioning.html 4 May 2003 06:30:02 -0000 1.8.2.8 +++ openacs-4/packages/acs-core-docs/www/eng-standards-versioning.html 7 May 2003 17:40:58 -0000 1.8.2.9 @@ -1,5 +1,5 @@ -Release Version Numbering
Prev Chapter�10.�Engineering Standards Next

Release Version Numbering

By Ron Henderson


+Release Version Numbering
Prev Chapter�10.�Engineering Standards Next

Release Version Numbering

By Ron Henderson


OpenACS docs are written by the named authors, and may be edited by OpenACS documentation staff.

@@ -36,7 +36,7 @@ particular release. To translate between a distribution tar file (acs-3.2.2.tar.gz) and a CVS tag, just swap '.' for '-' and add the release date. The entire release history of the toolkit is recorded -in the tags for the top-level readme.txt file: +in the tags for the top-level readme.txt file: 

 > cvs log readme.txt
 RCS file: /usr/local/cvsroot/acs/readme.txt,v
@@ -72,7 +72,7 @@

In the future, OpenACS packages should follow this same convention on version numbers. -

Transition Rules

So what distinguishes an alpha release from a beta +

Transition Rules

So what distinguishes an alpha release from a beta release? Or from a production release? We follow a specific set of rules for how OpenACS makes the transition from one state of maturity to the next.

Every release must pass the minimum requirements that it cleanly