Post sprint organization...
Dev Freeze = no new feature development. Developers shift to fixing bugs.
Code Freeze = current dev branch is completely frozen prior to deployment. All new dev work goes on a new branch for the next iteration.
Release date - generally, we aim for deploying on a Tuesday morning, so that folks are actually around if something breaks.
Sprint Number |
Dev Freeze Date |
Code Freeze |
Release Date |
Release Engineer |
---|---|---|---|---|
1 |
September 21, 2007 |
October 12 |
October 15/16 |
Robin |
2 |
October 29, 2007 |
November 1 |
November 5 |
Janet |
3 |
December 3, 2007 |
December 10 |
December 13/14 |
Qing |
4 |
January 4, 2008 everything except access control |
Jan 25, 2008 |
Jan 29, 2008 |
Janet |
5 |
March 11 2008 dev code freeze |
Jan 18, 2008 |
March 25, 26, 2008 |
|
Pre-sprint organization
Oct 2 Usability test
Oct 19 code freeze
Nove 19 release