Changes between Version 11 and Version 12 of PlumiReleaseManagement


Ignore:
Timestamp:
11/29/10 02:51:02 (3 years ago)
Author:
anna
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PlumiReleaseManagement

    v11 v12  
    99 * Development assigned and commenced with active scope management to move tickets in & out of a release depending on time/funds remaining 
    1010 * Code tested on Plumi development site http://testing.plumi.org 
     11 * Any bugs are added back to the milestone in Trac and fixed http://plumi.org/report/3 
    1112 * Code packaged by Unweb into a beta release and added to PyPI http://pypi.python.org/pypi/plumi.app/ 
    1213 * Announcements made (see below) 
     
    1718 * Ticket management (via plumi trac) & allocation (usually only bugs for an RC) http://plumi.org/report/3 
    1819 * Code tested on Plumi development site http://testing.plumi.org 
     20 * Any bugs are added back to the milestone in Trac and fixed http://plumi.org/report/3 
    1921 * Code packaged by Unweb into an RC and added to PyPI http://pypi.python.org/pypi/plumi.app/ 
    20  * Announcements made 
     22 * Announcements made (see below) 
    2123 * EngageMedia.org testing/staging site upgraded to RC for testing http://staging.engagemedia.org 
    2224 * Tickets specific to EngageMedia.org (on Redmine) are completed and EngageMedia.org testing/staging site updated with EM-specific code http://redmine.engagemedia.org http://staging.engagemedia.org 
     
    2931 * Final deployed to http://staging.engagemedia.org 
    3032 * EngageMedia.org staging site goes live for production at http://www.engagemedia.org  
    31  * Final announcements of the release 
     33 * Final announcements of the release (see below) 
    3234 
    3335== Announcements ==