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.42 -r1.43 --- openacs-4/packages/acs-core-docs/www/eng-standards-versioning.html 16 Feb 2005 00:21:02 -0000 1.42 +++ openacs-4/packages/acs-core-docs/www/eng-standards-versioning.html 4 Jun 2006 00:45:24 -0000 1.43 @@ -1,10 +1,11 @@ -Release Version Numbering
Alex logo
Prev Chapter�12.�Engineering Standards Next

Release Version Numbering

By Ron Henderson

Revised by Joel Aufrecht

+ +Release Version Numbering
Alex logo
Prev Chapter�12.�Engineering Standards Next

Release Version Numbering

By Ron Henderson

Revised by Joel Aufrecht

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

OpenACS version numbers help identify at a high-level what is in a particular release and what has changed since the last release. A -"version number" is really just a string of the form: +"version number" is really just a string of the form:

major.minor.dot[ milestone ]

  • A major number change indicates a fundamental change in the architecture of the system, e.g. OpenACS 3 to ACS 4. A major change is required if core backwards compatibility is broken, if upgrade is non-trivial, or if the platform changes substantially.

  • A minor change represents the addition of new functionality or changed UI.

  • A dot holds only bug fixes and security patches. Dot releases are always recommended and safe.

  • A milestone marker indicates the state of the release:

    • d, for development, means the release is in active development and is not in its intended released form.

    • a, for alpha, means new development is complete and code checkins are frozen. Alpha builds should work well enough to be testable.

    • b, for beta, means most severe bugs are fixed and end users can start trying the release.

    • Release Candidate builds (rc) are believed to meet all of the criteria for release and can be installed on test instances of production systems.

    • Final releases have no milestone marker. (Exception: In CVS, they are tagged with -final to differentiate them from branch tags.)

    Milestone markers are numbered: d1, d2, ..., a1, b1, rc1, etc.

A complete sequence of milestones between two releases: 

5.0.0