We would like to experiment with new weekly quality checkpoints, and
switch to four week milestones (maybe followed by a week of testing) in
this 0.6 release cycle. We will have at least two milestones before 0.6
release, but we are not yet sure on the exact number of milestones
before reaching the release.
As the names imply, the weekly quality checkpoints are quality driven.
They will happen every Monday morning, but may be delayed until
regression bugs have been fixed. (Haven't yet decided on naming
convention for these builds.)
Milestones are feature driven, but we are still aiming for a four week
cycle. (Note: quality still matters.)
Right now we are in spec writing mode. The clock for the milestone will
start on 25th.
There are several reasons why we'd like to try this approach:
* Try to maintain higher quality throughout; catch regressions earlier
* Simplify Aparna's workload and make it more explicit and frequent when
we will have what kind of testing
* Reduce the frequency and number of milestones to help with Bugzilla etc.
* Improve estimates by breaking feature work into these four week
milestones. They should be long enough to get features done, but still
frequent enough that we can estimate accurately. These will also act as
integration points and hopefully get feature work to land sooner rather
than later.
--
Heikki Toivonen
signature.asc
Description: OpenPGP digital signature
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
