wiki:PlumiReleaseManagement

Version 20 (modified by and, 4 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
  • Any bugs are added back to the milestone in Trac and fixed http://plumi.org/report/3
  • 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.

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:

Past Information

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