Since we've been using Bugzilla a lot more than before I think it is
finally starting to give some roughly usable statistics about fix rates
etc. we can use in planning, for example give us estimates of how long
will it take to fix a certain number of bugs or estimate when we could
achieve a release if we were to fix a certain number of bugs.
We still do a lot of checkins that don't have bugs assigned to them, and
do some other things which result in somewhat inaccurate numbers, so
these should be understood to just give us some ideas where we stand.
They should act as a reality check for us, though.
In 0.5 release cycle we fixed roughly 340 bugs, which were assigned to
23 people, or about 17 developers. 0.5 cycle lasted 5 months, so this
gives us a fix rate of about 4 bugs per developer per month.
We have 273 bugs targeted for 0.6 release. Assuming we'd have to fix
them all, have 20 developers working on them and each fixing 4 bugs per
month we'd be looking at 0.6 happening roughly three and a half months
from now.
--
Heikki Toivonen
signature.asc
Description: OpenPGP digital signature
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
