Version 2 (modified by grant, 7 years ago) (diff)


The Plumi Release Management Process involves the following steps:

  • Ticket management (via plumi trac) & allocation to a given release
  • Development assigned and commenced with active scope management to move tickets in & out of a release depending on time/funds remaining
  • Code tested on a development site (eg:
  • Code packaged into a beta release
  • Beta release deployed to for testing
  • Announcements made
  • If required, progress through multiple beta versions & release candidates until final version is completed
  • Code packaged into final
  • Final deployed to
  • Final announcements of the release

Making Announcements

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

  • Blog post on with a link back to the entry (if it's a beta/RC release) or the list of new features (if it's a final release)
  • Email to plumi-discuss and plumi-announce

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)

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