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.--what does this entail?--michaeltwofish 01:57, 13 December 2011 (UTC)
• Approval of the PMC to release.
• Grab translations from launchpad.
• Create a tag for the release from the release branch.
  • In habari/system:
    • git checkout 0.8 Checkout the release branch.
    • git tag -a v0.8 -m 'Version 0.8' Create an annotated tag for the release.
    • git push --tags origin 0.8 Publish the tag. Note that your remote might not be called origin.
  • In habari/habari:
    • git add system;git commit -m "Update system submodule to 0.8" Update the reference to the system submodule to point at the new tag.
    • git push origin master Publish the updated master. Again, your remote might not be called origin.
  • In habari/system:
    • git checkout master Checkout the master branch.
    • git merge 0.8 Merge the new tag into the master branch.
    • Edit system/classes/version.php to change to the next alpha, HABARI_VERSION = '0.9-alpha'.
    • git commit -a -m "Bump version to 0.9-alpha" Commit the version change.
    • Optionally git describe to show that master is now one commit ahead of the 0.8 tag.
    • git push origin master Publish the new tag and version update. And one more time, your remote still might not be called origin.
• 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.