Legend:
  • a fulfilled criterion
  • a deferred criterion
  • a failed criterion
  • an incomplete criterion
  • Feature Coding
    In order to complete feature coding, the following must be true:
    • There are no Priority 1 bugs for core packages.
    • 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 standard packages. 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.2.0a1)
    • Tag CVS with 5-2-0a1
    • Release alpha tarball

  • α testing
    In order to reach "Alpha Testing Complete" milestone, the following must be true:
    • There are no Priority 1 bugs for core packages.
    • There are less than 15 Pri 2 bugs for core.
    • 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

    At α-complete milestone, these tasks are required to produce a beta release for beta testing.
    • Set .info for all modified packages to beta1 (5.2.0b1)
    • Tag CVS with 5-2-0-b1
    • Release beta1 tarball

  • β testing
    In order to reach "Beta Testing Complete" milestone, the following must be true:
    • There are no Priority 1 bugs for core packages.
    • There are no Priority 2 bugs for core packages.
    • Outstanding Doc bugs fixed
    • Checkout is clean and the file protections are correct
    • Current work on translation server incorporated.
    • 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.2.0b2
    • Tag CVS with 5-2-0-rc1
    • Release rc1 tarball (optional)

  • Release Candidate testing
    In order to approve a Release Candidate, the following must be true:
    • RC installs cleanly on new server, including passing all automated testing
    • Successfully upgrades OpenACS.org
    • Successfully upgrades translate.openacs.org
    • 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.

Previous checklists