Release Status

Milestones and Milestone Criteria

Legend:

a fulfilled criterion
a deferred criterion
an incomplete criterion

5.0.4, released 10 March 2004

This release contains updated translations required for .LRN 2.0.2.

In order to release 5.0.4 the following must be true:

All 5.0.3 core message strings translated in German
CVS diff of oacs-5-0 branch vs openacs-5-0-3 reveals no unexpected code changes in core.
All Pri 1/2 bugs for 5.0.3 are fixed.
Candidate installs cleanly on new server, including passing all automated testing.
Documenter verifies docs updated

5.0.3, released 27 Feb 2004

In order to release 5.0.3 the following must be true:

CVS diff of oacs-5-0 branch vs openacs-5-0-2 reveals no unexpected code changes in core.
All Pri 1/2 bugs for 5.0.2 are fixed.
Candidate installs cleanly on new server, including passing all automated testing.
Documenter verifies docs updated
Andrew Grummet's changes with new message strings are complete and tested. (more info)

5.0.2, released 11 Feb 2004

In order to release 5.0.2 the following must be true:

CVS diff of oacs-5-0 branch vs openacs-5-0-1 reveals no unexpected code changes in core.
All Pri 1/2 bugs for 5.0.2 are fixed.
Candidate installs cleanly on new server, including passing all automated testing.
Documenter verifies docs updated

5.0.1, released 10 Feb 2004.

In order to release 5.0.1 the following must be true:

All translations from translation server incorporated.
CVS diff of oacs-5-0 branch vs openacs-5-0-0 reveals no unexpected code changes in core.
All Pri 1/2 bugs for 5.0.1 are fixed.
Candidate installs cleanly on new server, including passing all automated testing. (Several previously failing auto-tests continue to fail)
Documenter verifies docs updated

5.0.0, released 21 Jan 2004

Feature Coding completed 16 October 2003.
- New features code-complete
- Feature freeze announced on http://openacs.org/contribute/
α testing begun 16 Oct 2003, completed 11 Nov 2003.
In order to produce an alpha release, the following must be true:
- Can be installed manually
- All core packages have automated tests, not necessarily complete, and pass the tests.
  - acs-admin
  - acs-api-browser
  - acs-authentication
  - acs-automated-testing
  - acs-content-repository
  - acs-lang
  - acs-mail
  - acs-messaging
  - acs-service-contract
  - acs-subsite
  - acs-tcl
  - acs-templating
- all the core packages have upgrade scripts. (Kernel upgrade clarified in this forum post and in OCT chats)
- All core packages have current .info files
- All Severity 1 bugs fixed or postponed. (Postponed 375.)
- Checkin freeze (no code checked in without prior code review) announced
- CVS tagged: openacs-5-0-0b1.
- Tarball released: OpenACS 5.0.0b1 core, dotLRN 2.0.0b1.
- 11Dec2003 CVS tagged: openacs-5-0-0b4.
- Tarball released: OpenACS 5.0.0b4 core, dotLRN 2.0.0b4.
β testing begun 11 Nov 2003, completed 11 Jan 2004.
In order to produce a beta release,the following must be true:
- Documentation
  - Outstanding Doc bugs and pending errata fixed. (Mostly done; some postponed.)
  - Update major/minor versions in DocBook docs (in /packages/acs-core-docs/www/xml/variables.ent)
  - Regenerate .html docs from DocBook
  - Update readme.txt
  - Release notes current
- Checkout is clean and the file protections are correct
- Current work on translation server incorporated into cvs. (Postponed by TIP #35)
- No excessive notice/warning messages generated when running a server.
- Testing plan developed and executed for all core (and .LRN) packages. (Not accomplished for .LRN)
- All Severity 1 and Severity 2 bugs fixed or postponed.
- CVS tagged with "b"
- Tarball released
Release Candidate testing begun 11 Jan 2004, completed 21 Jan 2004
In order to produce a release candidate the following must be true:
- Translation server data synchronized to branch. (Postponed - see previous)
- RC installs cleanly on new server, including passing all automated testing
- Successfully upgrades OpenACS.org (deferred until after 5.0)
- Test team verifies no blocking bugs
- Documenter verifies docs updated
Release. Version 5.0.0 begun 1 June 2003, released 21 Jan 2004.
In order to declare a release candidate to be a final release, the following must be true
- Release candidate is available for one week without any severity 1 bugs being reported
- In .info for all core packages, version updated to 5.0.0, release date set to today; acs-core-docs variables.ent updated to 5.0.0, release-notes updated, and docs regenerated; readme.txt updated
After a release candidate is declared final, the following tasks must be performed:
- version added to SDM
- OpenACS.org links updated (on home page, openacs project page)
- Documentation updated on web
- Announcement posted in News