launchpad-dev team mailing list archive

[Curtis Hovey <curtis.hovey@xxxxxxxxxxxxx>]

On Thu, 2011-01-13 at 18:02 -0500, Francis J. Lacoste wrote:
> On January 12, 2011, Curtis Hovey wrote:
> > The average engineer closes 5 bugs a month. 8 engineers on maintenance
> > will close about 40 critical bugs. We have just under 10 months of
> > critical bugs assuming no other critical bugs are add.
> 
> Your average is a little bit conservative. Since April, we are _fixing_ about 
> 194 bugs a month, that's 7 per engineer. If we look at the number of bugs 
> _closed_ (average 273 per month), it goes up to 10.

Your numbers are skewed because many bugs were closed as a part or
retriage at the end of the year. I personally closed more than 100 bugs
in November. I do not think that 10 is sober since we need to take more
engineers off coding to find the duplicates and already fixed.

I think median is a better number to use since a few engineers are
throwing off the curve. If they are not on maintenance the velocity will
fall. Good news for you though, the 3 of the top five are on maintenance
to start this off.

> We have 59 time outs currently. This means that with the maintenance squads we 
> can probably burn down the time out categories in a little more than a month!  
> Then we have 165 oops. I contend that we don't need to fix most of these. 
> There a lot of those that are probably not relevant anymore. Using the closing 
> rate, we can burn down those in probably two more months. (And that's assuming 
> a conservative ratio of 3 invalid for 7 fixes required. I'm sure that ratio is 
> higher for OOPSes)

Timeouts are hard to close, even for people like me. I can close an oops
in less than a day, but I think I can fix only 2 timeouts per week. The
oopses the Registry team have worked on last year were not invalid, I do
not expect to close invalid oopses. We were able to fix a few timeouts
by finding a common root cause. I think 2 our of 7 timeouts have common
roots.


-- 
__Curtis C. Hovey_________
http://launchpad.net/

Attachment: signature.asc
Description: This is a digitally signed message part