Changes between Version 11 and Version 12 of PlumiReleaseManagement

Timestamp:

11/29/10 02:51:02 (2 years ago)

Author:

anna

Comment:

--

PlumiReleaseManagement

@@ -9 +9 @@
  * 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)
@@ -17 +18 @@
  * Ticket management (via plumi trac) & allocation (usually only bugs for an RC) http://plumi.org/report/3
  * 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 an RC and added to PyPI http://pypi.python.org/pypi/plumi.app/
- * Announcements made
+ * Announcements made (see below)
  * EngageMedia.org testing/staging site upgraded to RC for testing http://staging.engagemedia.org
  * 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
@@ -29 +31 @@
  * Final deployed to http://staging.engagemedia.org
  * EngageMedia.org staging site goes live for production at http://www.engagemedia.org 
- * Final announcements of the release
+ * Final announcements of the release (see below)
 
 == Announcements ==