Legend:
- a fulfilled criterion
- a deferred criterion
- a failed criterion
- an incomplete criterion
- Feature Coding completed 12 March 2004.
In order to complete feature coding, the following must be true:- There are no Priority 1 bugs for core or
standardpackages. (criterion for standard packages deferred for 5.1) - New features code-complete
- New features code and api-docs committed on HEAD
- New features pass automated tests on integration server
- ACS Core can be installed manually
- ACS Core can be installed by automated installer and pass all automated tests
For the time period from the feature coding deadline to meeting the feature-complete criteria, HEAD is feature-frozen for core
and standardpackages. This means no new features can be committed, only bug fixes.At code-complete milestone, these tasks are required to produce an α release for α testing.
- Create new minor branch from CVS HEAD
- Announce feature freeze (no commits to new branch except in response to bugs) on branch on http://openacs.org/contribute/
- Set .info for all modified packages to alpha1 (5.1.0a1)
- Tag CVS with 5-1-0a1, skipped
- Release alpha tarball (optional, skipped)
- There are no Priority 1 bugs for core or
- α testing completed 26 March 2004.
In order to reach "Alpha Testing Complete" milestone, the following must be true:- Priority 1 bugs for core
or standardpackages. - There are less than 15 Pri 2 bugs for core. (There are 21, but 15 are resolved and only 6 are open)
- All core packages have automated tests, and pass the tests.
- All the core packages have upgrade scripts and can be upgraded from last release via APM
- All core packages have current .info files
- Release notes and Changelog current (skipping this step)
At α-complete milestone, these tasks are required to produce a beta release for beta testing.- Set .info for all modified packages to beta1 (5.1.0b1)
- Tag CVS with 5-1-0-b1
- Release beta1 tarball (optional, skipped)
- Priority 1 bugs for core
- β testing completed 19 April 2004.
In order to reach "Beta Testing Complete" milestone, the following must be true:- There are no open Priority 1 for core
or standardpackages for the pending release. - There are no open Priority 2 bugs for core
or standardpackages for the pending release. - Outstanding Doc bugs fixed
- Checkout is clean and the file protections are correct
- Current work on translation server incorporated. No new translation work incorporated since 5.0.4.
- No excessive notice/warning messages generated when installing or running a server.
- Testing plan executed for all core (and .LRN) packages.
- Release notes and Changelog current
At β-complete milestone, these tasks are required to produce a release candidate for RC testing.- Update versions in DocBook docs (in /packages/acs-core-docs/www/xml/variables.ent)
- Regenerate .html docs from DocBook
- Update readme.txt
- Set .info for all modified packages to 5.1.0rc1 (N.B. - currently breaks APM - used b2)
- Tag CVS with 5-1-0-rc1
- Release rc1 tarball (optional)
- There are no open Priority 1 for core
- Release Candidate testing 19 April - 29 April 2004. 5.1.0 Released 29 April 2004.
In order to approve a Release Candidate, the following must be true:- RC installs cleanly on new server, including passing all automated testing (several automated tests fail - these correspond to non-critical bugs)
- Successfully upgrades OpenACS.org - Deferred
- Test team verifies no blocking bugs
- Documenter verifies docs updated
- Release candidate is available for one week without any Priority 1 or 2 bugs being reported
At Release milestone, these tasks are required to produce a Release.- In .info for all core packages, version updated to 5.1.0; release date set to today; Documentation updated to new version number; release-notes updated; readme.txt updated
- version added to SDM
- OpenACS.org links updated (on home page, openacs project page)
- Documentation updated on openacs.org
- Announcement posted in News