Free DVDs!

[Carthik Sharma]

On 12/12/06, Christian Robottom Reis <kiko at async.com.br> wrote:
>
> To ensure the message is across: we want both confirmation (or
> invalidation) of bugs, and indication of what source package(s) they are
> related to. You get extra good vibes if you add upstream bug watches for
> the upstream bugs, but the thing I'm really looking for is confirmation
> and source package indication.

I have tried my hand at tackling this exact subset of bugs before. The
biggest problem is that a majority of the bugs cannot be assigned a
package -- "Ubuntu" -- best describes where the bug belongs. A bug
entitled "(K)Ubuntu crashes frequently" is one example. Others deal
with specific laptops/hardware and so it may not be evident which
package the bug belongs to. My rough estimate is that about 100-200
bugs of the lot will be of this kind - where a package isn't obvious.

> On Tue, Dec 12, 2006 at 02:17:34PM +0100, Henrik Nilsen Omma wrote:
> > I think zero is a difficult task though because two new ones will always
> > sneak in at the end. But you can of course determine that by looking at
> > the dates.
>
> You're right -- but I want to see that number get down to one digit, and
> stay there. I know there is a lot of up-front work that needs to be
> done, which is why I'm putting up this bounty (and also because movies
> are always good karma!), but I want us to keep the number down once
> we're there! I'll be okay with is stipulating an error margin of 20
> bugs, but I'll be even happier with a hard zero!

Nice bounty though! Let me take a crack at getting there :)

Carthik.

-- 
Ph.D. Candidate
University of Central Florida
Homepage: http://carthik.net