Changes between Version 4 and Version 5 of PlumiReleaseManagement


Ignore:
Timestamp:
10/11/10 16:17:47 (4 years ago)
Author:
and
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PlumiReleaseManagement

    v4 v5  
    44The Plumi Release Management Process involves the following steps: 
    55 
    6  * Ticket management (via plumi trac) & allocation to a given release 
    7  * Development assigned and commenced with active scope management to move tickets in & out of a release depending on time/funds remaining 
    8  * Code tested on a development site (eg: latest-v.plumi.org) 
    9  * Code packaged into a beta release 
    10  * Beta release deployed to demo.plumi.org for testing 
    11  * Announcements made 
    12  * If required, progress through multiple beta versions & release candidates until final version is completed 
    13  * Code packaged into final 
    14  * Final deployed to demo.plumi.org 
    15  * Final announcements of the release 
     6 # Ticket management (via plumi trac) & allocation to a given release 
     7 # Development assigned and commenced with active scope management to move tickets in & out of a release depending on time/funds remaining 
     8 # Code tested on a development site (eg: latest-v.plumi.org) 
     9 # Code packaged into a beta release 
     10 # Beta release deployed to demo.plumi.org for testing 
     11 # Announcements made 
     12 # Testing.engagemedia.org upgraded to beta for testing and deployment to engagemedia.org 
     13 # If required, progress through multiple beta versions & release candidates until final version is completed 
     14 # Code packaged into final 
     15 # Final deployed to demo.plumi.org  
     16 # Final announcements of the release 
    1617 
    1718=== Making Announcements ===