Changes between Version 2 and Version 3 of WorkflowPolicy


Ignore:
Timestamp:
09/07/10 13:30:00 (11 years ago)
Author:
jdreed
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WorkflowPolicy

    v2 v3  
    1010== Committing Code == 
    1111 
    12 Prereq: Changes tested by developer. 
    13 TTL: 2 business days 
     12 * Prereq: Changes tested by developer. 
     13 * TTL: 2 business days 
    1414 
    1515Anyone with repository access may commit code changes.  When appropriate, new Changelog entries should be created.  If you do not intend to immediately upload the package, the Distribution should be listed as "UNRELEASED".   
     
    2121== Uploading to Alpha (development) == 
    2222 
    23 Prereq: Explicit ACK or commit TTL exceeded. 
    24 TTL: n/a 
     23 * Prereq: Explicit ACK or commit TTL exceeded. 
     24 * TTL: n/a 
    2525 
    2626Once code has been approved or the TTL has exceeded, it may be built and uploaded to the alpha (`development`) repository.  At this point, it should be tested by as many developers as possible.  Code requires 2 explicit ACKs to proceed to the next stage.  An ACK may occur in a Trac comment; a reply to a Trac e-mail, or a zephyr to debathena,apt,* with a body indicating the ACK and the package name and version. 
     
    2828== Uploading to Beta (proposed) == 
    2929 
    30 Prereq: Two explicit ACKs while in alpha stage. 
    31 TTL: 3 business days 
     30 * Prereq: Two explicit ACKs while in alpha stage. 
     31 * TTL: 3 business days 
    3232 
    3333Once the changes have been approved in Alpha, the package is moved to the beta (`proposed`) repository.  At this point, it is now available to the general public (e.g. beta machines in W20).  Any developers who have not already tested the package should do so.  A package must remain in proposed for up to 3 business days, unless it receives explicit approval from IS&T development and support.   
     
    3535== Upload to Production == 
    3636 
    37 Prereq: (Explicit approval OR beta TTL expiration) AND ( ( today != Friday ) AND ( today != day_before_institute_holiday ) ) 
     37 * Prereq: (Explicit approval OR beta TTL expiration) AND ( ( today != Friday ) AND ( today != day_before_institute_holiday ) ) 
    3838 
    3939Once the beta TTL has expired or approval has been obtained, the package may be moved to the production repository.  This should not happen on Fridays or days before Insitute holidays without discussion by release-team.