From: Jeff Garzik <jgarzik@pobox.com>
To: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Yay, bug tracking! (was Re: Bug tracking in the run up from 2.5 to 2.6)
Date: Mon, 21 Oct 2002 21:08:46 -0400 [thread overview]
Message-ID: <3DB4A51E.3040405@pobox.com> (raw)
In-Reply-To: 205680000.1034895125@flay
Martin J. Bligh wrote:
> We're proposing to create a bug tracking system to help keep track of
> 2.5 kernel bugs ... in an attempt to help get 2.5 stabilised as quickly as
> possible.
> It would be based on Bugzilla, and open for anyone to log bugs against
> 2.5, though those would then be filtered by a set of "maintainers" to keep
> the quality of the data up to snuff. Ideally those would be the subsystem
> maintainers as we know them now, though in the event that certain people
> weren't interested, we'd find a "bugzilla maintainer" for the subsystem to
> fill that role.
This is fantastic.
This is one of the things I think the Linux kernel sorely lacks, both
image-wise and practically-speaking. Ted T'so maintained a bug list for
a while, and it was (a) valuable and (b) way too much work for one human
to possibly handle.
> IBM's Linux Technology Centre is willing to provide the machine, admin,
> and people to help maintain the data in the database. We have someone
> who's kindly agreed in principle to host the machine for us (feel free to
> speak up if you like, otherwise I'll wait until the proposal is firmed up).
Again, fantastic. As was discussed at the original Kernel Summit (and
perhaps the latest one as well?), everyone knows we need a bug tracking
system, but without humans to help keep the garbage bug reports to a
minimum, the system won't be used by developers _or_ users with
legitimate problems.
> We'll also have a slew of engineers dedicated to stabilise 2.5 after the
> freeze, but this is not intended to be solely an IBM thing by any means;
> we're volunteering to host the tracking database on behalf of the community,
> and do some of the dirty work of administration. The intent is to have this
> up and running by Halloween, and for a signification cross-section of the
> community to use it.
>
> So ... are the maintainers interested in working with this kind of system?
I certainly am. Even though I claim to be net driver maintainer, I
don't begin to claim that I can track and fix _all_ bugs in _all_ net
drivers, even though I endeavor to do the best I can.
This Bugzilla system, I believe, should help a great deal.
I'm definitely willing to give it an honest shot with net drivers, and I
hope that we can persuade others to do so as well.
One suggestion - it might be nice for IBM to register "linuxbugs.org" or
bugzilla.kernel.org or similar, so to provide an additional impression
of impartiality. I don't mind "Hosted by IBM!" plastered all over the
site, but if Bugzilla ever needs to move, that makes things much easier.
Jeff
next prev parent reply other threads:[~2002-10-22 1:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-17 22:52 Bug tracking in the run up from 2.5 to 2.6 Martin J. Bligh
2002-10-17 23:02 ` Timothy D. Witham
2002-10-18 13:41 ` mgross
2002-10-17 23:15 ` Greg KH
2002-10-17 23:47 ` Martin J. Bligh
2002-10-17 23:52 ` Zwane Mwaikambo
2002-10-18 0:08 ` Martin J. Bligh
2002-10-20 15:34 ` Arnaldo Carvalho de Melo
2002-10-19 12:48 ` Adrian Bunk
2002-10-20 15:22 ` Martin J. Bligh
2002-10-22 1:08 ` Jeff Garzik [this message]
2002-10-22 1:40 ` Yay, bug tracking! (was Re: Bug tracking in the run up from 2.5 to 2.6) Rik van Riel
2002-10-22 1:43 ` Martin J. Bligh
2002-10-22 9:49 ` Alan Cox
2002-10-22 9:37 ` Jeff Garzik
2002-10-24 18:34 ` Cliff White
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3DB4A51E.3040405@pobox.com \
--to=jgarzik@pobox.com \
--cc=Martin.Bligh@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox