Re: Linux 2.6.21

On Thu, Apr 26, 2007 at 02:13:08PM -0700, Linus Torvalds wrote:
...
(I've said this before, but I'll say it again: one thing that would
already make bugzilla better is to just always drop any bug reports that
are more than a week old and haven't been touched. It wouldn't need *much*
touching, but if a reporter cannot be bothered to say "still true with
current snapshot" once a week, then it shouldn't be seen as being somehow
up to those scare resources we call "developers" to have to go through
it).
...

And if it's a bug in an unmaintained subsystem, a user could do this for
100 weeks without any effect.
There's no value in keeping reporters busy with useless tasks. [1]

Don't forget:
A good bug report is an important contribution.

We are already quite good at ignoring bug reports that come through
linux-kernel, and it's an _advantage_ of the kernel Bugzilla to see more
than 1600 open bugs because this tells how bad we are at handling bugs.
How many thousand bug reports have been ignored during the same time on
linux-kernel?

If a developer asked for further information and the submitter didn't
answer within 1 months, I will close this bug. [2] And "I will" is not
talking about the future, I'm doing this in the kernel Bugzilla for
three years or so.

The problem is we have tree states of subsystems and drivers:
- unmaintained
- maintained [3]
- maintained and maintainer looks after bug reports

I do hereby promise you to manually ask the submitters of all 1600 open
bugs in the kernel Bugzilla within one month whether their problem is
still present with 2.6.21 and forwarding all bugs if the answer was
"yes" to whoever is the right recipient if you promise me that all bugs
where the submitter said "yes" will be debugged by a kernel developer
who knows the corresponding subsystem. [4]

Limis

cu
Adrian

[1] "Still present with the latest kernel?" is a valid question
if a developer intends to debug further, but otherwise it's silly.
[2] sometimes a bit later, but I'll do it
[3] I'll not do public maintainer bashing, but we have very active
maintainers with nearly zero activity in debugging user bug reports
[4] I don't think you'll do - but if you do that's a serious offer

--

"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed

-
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: [Slightly OT] Re: Ranter or evangelist?
    ... Brasero and Totem and I'd rather not reinstall them and then having each ... What is your success with filing bug reports? ... I never had any success convincing the bugzilla interface. ... Do you really believe developers need to be advised ...
    (Fedora)
  • Re: Installing FC5 on pre-partitioned /dev/hdb
    ... seems to me that since Red Hat and Fedora absolutely rely upon ... bugzilla for bug reports and repairs, ... endless loop of searching for old bug reports that fit my description ...
    (Fedora)
  • Re: ABRT is not reporting my bugs
    ... yet I cannot find the bug reports in Bugzilla. ... oopses to the Fedora bugzilla, to be vetted by the kernel maintainers, ... before passing the oopses upstream. ...
    (Fedora)
  • Re: ABRT is not reporting my bugs
    ... yet I cannot find the bug reports in Bugzilla. ... Although I understand that patching upstream content in Fedora is ... oopses to the Fedora bugzilla, to be vetted by the kernel maintainers, ...
    (Fedora)
  • Re: Linux 2.6.21
    ... We are already quite good at ignoring bug reports that come through ... than 1600 open bugs because this tells how bad we are at handling bugs. ... it just shows that bugzilla doesn't matter for most of the kernel. ... doesn't care I don't care and I'll work on things that people do care ...
    (Linux-Kernel)