Changes between Version 1 and Version 2 of PlumiReleaseManagement


Ignore:
Timestamp:
08/10/10 09:36:50 (4 years ago)
Author:
grant
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PlumiReleaseManagement

    v1 v2  
    11The Plumi Release Management Process involves the following steps: 
    22 
    3 * Ticket management (via plumi trac) & allocation to a given release 
    4 * Development assigned and commenced with active scope management to move tickets in & out of a release depending on time/funds remaining 
    5 * Code tested on a development site (eg: latest-v.plumi.org) 
    6 * Code packaged into a beta release 
    7 * Beta release deployed to demo.plumi.org for testing 
    8 * Announcements made 
    9 * If required, progress through multiple beta versions & release candidates until final version is completed 
    10 * Code packaged into final 
    11 * Final deployed to demo.plumi.org 
     3 * Ticket management (via plumi trac) & allocation to a given release 
     4 * Development assigned and commenced with active scope management to move tickets in & out of a release depending on time/funds remaining 
     5 * Code tested on a development site (eg: latest-v.plumi.org) 
     6 * Code packaged into a beta release 
     7 * Beta release deployed to demo.plumi.org for testing 
     8 * Announcements made 
     9 * If required, progress through multiple beta versions & release candidates until final version is completed 
     10 * Code packaged into final 
     11 * Final deployed to demo.plumi.org 
     12 * Final announcements of the release 
     13 
     14=== Making Announcements === 
     15 
     16Whenever a new version of Plumi is released, the following announcements are made: 
     17 
     18 * Blog post on blog.plumi.org with a link back to the plone.org entry (if it's a beta/RC release) or the list of new features (if it's a final release) 
     19 * Email to plumi-discuss and plumi-announce 
     20 
     21If the release is a "final release" of a new version, the following additional steps are taken: 
     22 
     23 * Update the "Download" button on the top right hand column of blog.plumi.org to show the release number & file size (edit the sidebar.php template in WordPress) 
     24 * Update the Download page in blog.plumi.org to reflect the new version number, the Plone version it bundles and a link to the release announcement on the plumi blog 
     25 * Update the plumi wiki start page to reflect the new version 
     26 * Attach the new version's tarball file to the plumi wiki start page (& remove the previous version's file) 
    1227 
    1328