Changes between Version 7 and Version 8 of WorkflowPolicy
- Timestamp:
- 01/05/11 15:49:04 (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
WorkflowPolicy
v7 v8 23 23 Once 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 (one of which can be the original author) 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. 24 24 25 Active developers should have easy access to a machine in the Alpha cluster. IS&T-public Alpha machines are located in N42 (`cheshire-cat.mit.edu`) and the test cluster (`<FIXME>.mit.edu`).25 Active developers should have easy access to a machine in the Alpha cluster. IS&T-public Alpha machines are located in N42 (`cheshire-cat.mit.edu`) and the W92 test cluster (`{breakout|gorf}.mit.edu`). 26 26 27 27 == Uploading to Beta (proposed) ==