Hi all,
I think we are ready to move into the 'feature freeze' portion of the release cycle, as we had anticipated last week.
In this phase, the focus should be on bug fixing only, not on adding features, nor code cleanup or optimization. The length of this phase will be controlled by how quickly we can gain closure on enough of the critical bugs.
There's currently 85 bugs, with about 20 bugs at the critical priority level. I think a reasonable goal would be to reduce the critical bug count to 10 or fewer. It would also be nice to reduce our bug open/total percentage from its current 18% to 15%.
Bryce
On Sat, 26 Jun 2004, Bryce Harrington wrote:
It feels like things are getting close to being ready for a freeze, and to start preparing for the release. There's a lot of work still going on, and we don't want to interrupt things abruptly, so it may be worthwhile to settle on some loose target dates. How does the following plan sound?
'Feature chill' - June 28. No new features should be started, work should be wrapping up on existing features and code cleanup. Unfinished features should be hidden. Focus should be on bug fixing.
'Feature freeze' - Sometime in first week of July. Only bug fixing should occur after this point. Focus should be on closing critical bugs and bugs in new features.
'Hard freeze' - When all major bugs have been closed that we intend to close, we go into a short hard freeze period for a few days where no changes are allowed except under strict change control. We do final QA, verify on as many platforms as possible, create the packages and verify they work well, and make sure no last minute bugs slipped in.
'Release'
Bryce