Release Checklist

From Habari Project

Revision as of 03:02, 23 November 2011 by Michaeltwofish (Talk | contribs)
Jump to: navigation, search

These are the steps that need to be taken when preparing each new release:

  • Freeze new features by creating a release branch. See Release Policy for more information about types of releases, including where they are branched from and how long they should be frozen before release.
    • Update version.php with the new release version.
    • Notify testers and 3rd-party developers of the upcoming release. Notify translators so they can update with any changes.
    • Following the Test Procedure, check each feature.
  • Audit the files for security issues.
  • Build the release documentation:
    • Write the release notes.
      • Summarize issues fixed - need not be comprehensive (include Trac report URL).
      • Summarize features added.
    • Write the upgrading process, include any necessary files.
    • Update the user manual.
  • Approval of the PMC to release.
  • Grab translations from launchpad.
  • Create a tag for the release from the release branch.
  • Prepare the release package.
    • Update version references.
    • Deploy release archive to download location.
    • Update the version number for the update beacon on hp.o
  • Upgrade the demo site to the new version.
  • Announce the release on our home page, wiki, and mailing lists.
  • Celebrate!
  • Start work for next release
Personal tools