Release Management Process

Testing Checklist

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
  • Any bugs are added back to the milestone in Trac and fixed
  • 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:

Past Information

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