Re: Linux 2.6.21

Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> writes:

On Sun, 29 Apr 2007, Adrian Bunk wrote:

That's exactly where Linus' "drop any bug reports that are more than a
week old" suggestion is completely flawed - no matter what the submitter
does, how often he tests latest kernels, noone will help him.

You talk, but what do you actually *suggest*?

Talk is cheap. You use to do the walk too, but you've already said that
you're not interested in that any more. So excuse me if I'm not impressed.

The thing is, bugzilla is totally broken because it's designed to help
track bugs, but it's *not* designed to actually handle the much harder
problem, which is to actually get the *right* developers to be aware of
the *right* bugs!

This means we need people who figure out who to assign bugs too.
Aka bugmasters.

In theory it could be nearly automated. Figure out what files related
to the bug and assign to the last 5 people who submitted patches
for them and/or signed off.

Ok I suppose it's not that easy -- you would need some human judgement.

BTW one big problem in our current bugzilla is that a lot of people
cannot reassign bugs they don't own. I sometimes see bugs that I don't
own bug I know who is responsible, but bugzilla doesn't allow me to do it.

So I think what would help:

- Ask more people to just categorize and reassign bugs (anybody interested?)
- Give more people in bugzilla the power to reassign arbitary bugs
(bugzilla maintainers would need to do that)

-Andi

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Relevant Pages

  • Re: kernel bugzilla is FPOS (was: Re: "buggy cmd640" message followed by soft lockup)
    ... use bugzilla only for long-term bugs and avoid the needless bureaucracy. ... It looks like you'd like the reporter to initially debug the issue for you ... the bugreport status before filling bugzilla entry). ...
    (Linux-Kernel)
  • kernel bugzilla is FPOS (was: Re: "buggy cmd640" message followed by soft lockup)
    ... use bugzilla only for long-term bugs and avoid the needless bureaucracy. ... I put all of the reported regressions into the Bugzilla early. ... "Kernel version" given by reporter should be checked against the latest ...
    (Linux-Kernel)
  • Bugzilla and management thereof
    ... reporting it to bugzilla. ... the report could be updated to note that it still applies to f7. ... auto-closes bugs from older releases*. ... I was assuming that if Ray decided it was an upstream bug he'd ...
    (Fedora)
  • Re: [BUG] New Kernel Bugs
    ... of the biggest problems with bugzilla. ... Virtually no one in the ARM ... community looks for ARM bugs in bugzilla. ... the number of arm-specific reports in there is very small. ...
    (Linux-Kernel)
  • Re: MODULE_MAINTAINER
    ... ever gone to bugzilla without killing well over ... used for a report) to search for similar reports and join them. ... bugs and then simply mark them as such once identified. ... As subsystem maintainer, I am actively using kernel.org's bugzilla and I ...
    (Linux-Kernel)