Talk:Release 0.8

From Habari Project

• Freeze new features by creating a release branch.
  • 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. --what does this mean?--michaeltwofish 22:07, 12 December 2011 (UTC)
  • 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.