[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.63.0704282339220.11975@qynat.qvtvafvgr.pbz>
Date: Sat, 28 Apr 2007 23:43:09 -0700 (PDT)
From: David Lang <david.lang@...italinsight.com>
To: David Miller <davem@...emloft.net>
cc: mrechberger@...il.com, torvalds@...ux-foundation.org,
bunk@...sta.de, diegocg@...il.com, cebbert@...hat.com,
linux-kernel@...r.kernel.org
Subject: Re: Linux 2.6.21
On Sat, 28 Apr 2007, David Miller wrote:
>
> From: "Markus Rechberger" <mrechberger@...il.com>
> Date: Sun, 29 Apr 2007 00:58:09 +0200
>
>> On 4/29/07, Linus Torvalds <torvalds@...ux-foundation.org> wrote:
>>>
>>>
>>> On Sat, 28 Apr 2007, Adrian Bunk wrote:
>>>>
>>>> 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.
>>>
>>> No, it just shows that bugzilla doesn't matter for most of the kernel.
>>>
>>> Don't say that "bugzilla tells how bad we are at handling bugs". It tells
>>> how bad *bugzilla* is for handling bugs, nothing more.
>>>
>>
>> I totally disagree here, bugzilla is a very good tool.
>
> No, Bugzilla really does suck, and I personally refuse to use it when
> I have a choice. And guess what? You better be concerned about that
> because I maintain all of the networking code :-)
>
> It puts the onus FAR too much on the developer and not enough on the
> reporter and other minions. We have a small resource of developers,
> yet lots of users, bug reporters, and minions, so something that
> doesn't take advantage of the larger resource we have is going to
> not function efficiently at all. Yet that is what bugzilla does.
I'll say that as a user I hate having to deal with bugzilla.
there's nothing more frustrating then spending a good chunk of time trying to
find a similar bug, then jumping through all the bugzilla hoops to file a report
to eventually (days/weeks later) get a message 'closed becouse it's a duplicate
report), then have to go and track down what it's a duplicate of, read through
that bug report, only to find that it's not solved there either, and to top it
off, the people working on that bug won't see my report or that I'm available to
troubleshoot it.
from a user poit of view, e-mailing the kernel list (retrying a few days later
of there is no response) tends to work _much_ better.
David Lang
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists