launchpad-dev team mailing list archive
-
launchpad-dev team
-
Mailing list archive
-
Message #05738
Re: high bugs - doing a bit of a review
On Fri, 2010-11-19 at 04:02 +1300, Robert Collins wrote:
> I want to get a better idea of what we've classified as high - as such
> I'm wandering through them all, and I may touch/downgrade whatever
> some of your pet bugs : if I do, and you disagree, please do put them
> to how you want them. I won't be downgrading them when the status is
> fresh etc : I'm not aiming to create any makework for folk, and I
> won't dispute if you toggle something back (or lower it further, etc).
We only work on High bugs. I believe all high bugs should be targeted to
a milestone to show we are planning to work on it in the near future. If
a high bug is not ready to code, we are getting it ready to code, so
targeting to an feature/series milestone is often the right thing to do.
(If I could untarget from a series, I would suggest targeting to a
series).
Most high bugs are not high because we do not intend to work on them
even in the next year. I believe all the bugs were high, but we
neglected to update them as our priorities changed.
the Lp team fixes ~100 high bugs each month, of which about 15 are over
a year old. There are about 700 high bugs, 300 of which are older than a
year. It will take us 20 releases to close these bugs if we do not
reprioritise...but we have...there are 93 oopes and timeouts not set as
High.
--
__Curtis C. Hovey_________
http://launchpad.net/
Attachment:
signature.asc
Description: This is a digitally signed message part
References