Version 11 (modified by and, 5 years ago) (diff)


Release Management Process

The Plumi Release Management Process involves the following steps:


  • Ticket management (via plumi trac) & allocation (generally inclusive of new features with an alpha or beta)
  • 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
  • Code packaged by Unweb into a beta release and added to PyPI
  • Announcements made (see below)
  • 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 only




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 to show the release number & file size (edit the sidebar.php template in WordPress?)
  • Update the Download page in 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 -
  • Update Freshmeat page -

Past Information

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