wiki:PlumiReleaseManagement

Version 1 (modified by grant, 4 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: latest-v.plumi.org)
  • Code packaged into a beta release
  • Beta release deployed to demo.plumi.org 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 demo.plumi.org

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