Changes between Version 6 and Version 7 of PlumiReleaseManagement


Ignore:
Timestamp:
11/29/10 02:18:56 (2 years ago)
Author:
anna
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • PlumiReleaseManagement

    v6 v7  
    44The Plumi Release Management Process involves the following steps: 
    55 
    6  * Ticket management (via plumi trac) & allocation to a given release 
     6=== ALPHA or BETA === 
     7 
     8 * Ticket management (via plumi trac) & allocation (generally inclusive of new features with an alpha or beta) http://plumi.org/report/3 
    79 * 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 
     10 * Code tested on a development site http://testing.plumi.org 
     11 * Code packaged into a beta release http://pypi.python.org/pypi/plumi.app/#downloads 
     12 * Announcements made (see below) 
     13 * EngageMedia.org testing/staging site upgraded to alpha or beta for testing - only if more test data desired or other specific reason http://staging.engagemedia.org 
     14 
     15=== RC === 
     16 
     17* Ticket management (via plumi trac) & allocation (usually only bugs for an RC) http://plumi.org/report/3 
     18 * Code tested on a development site http://testing.plumi.org 
     19 * Code packaged into a beta release http://pypi.python.org/pypi/plumi.app/#downloads 
    1120 * 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 
     21* EngageMedia.org testing/staging site upgraded to RC for testing - only if more test data desired or other specific reason http://staging.engagemedia.org 
     22 * Tickets specific to EngageMedia.org (on Redmine) are completed and EngageMedia.org testing/staging site updated http://redmine.engagemedia.org http://staging.engagemedia.org 
     23 * If required, progress through multiple release candidates until final version is completed 
     24 
     25=== FINAL === 
     26 
    1427 * Code packaged into final 
    1528 * Final deployed to demo.plumi.org  
    1629 * Final announcements of the release 
    1730 
    18 === Making Announcements === 
     31== Making Announcements == 
    1932 
    2033Whenever a new version of Plumi is released, the following announcements are made: