wiki:PlumiReleaseManagement

Version 10 (modified by anna, 3 years ago) (diff)

--

Release Management Process

The Plumi Release Management Process involves the following steps:

ALPHA or BETA

  • Ticket management (via plumi trac) & allocation (generally inclusive of new features with an alpha or beta) http://plumi.org/report/3
  • Development assigned and commenced with active scope management to move tickets in & out of a release depending on time/funds remaining
  • Code tested on Plumi development site  http://testing.plumi.org
  • Code packaged by Unweb into a beta release and added to PyPI  http://pypi.python.org/pypi/plumi.app/
  • Announcements made (see below)
  • EngageMedia.org testing/staging site upgraded to alpha or beta for testing - only if more test data desired or other specific reason, otherwise further development continues on testing.plumi.org only  http://staging.engagemedia.org

RC

FINAL

Announcements

Whenever a new version of Plumi is released, the following announcements are made:

If the release is a "final release" of a new version, the following additional steps are taken:

  • Update the "Download" button on the top right hand column of blog.plumi.org to show the release number & file size (edit the sidebar.php template in WordPress?)
  • Update the Download page in blog.plumi.org to reflect the new version number, the Plone version it bundles and a link to the release announcement on the plumi blog
  • Update the plumi wiki start page to reflect the new version
  • Attach the new version's tarball file to the plumi wiki start page (& remove the previous version's file)
  • Update wikipedia page -  http://en.wikipedia.org/wiki/Plumi

Past Information

Here's the steps we followed when we were migrating EngageMedia.org to Plumi 3.