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
On Mon, 21 Oct 2002, Jeff Garzik wrote:
> 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.
>
> This is fantastic.
<AOL/>
Count me in as a participant. One thing that would be nice is
a mailing list where the bugs (and the changes to bugs) get
mailed, so we can get updates by email.
I'll help track down, fix and admin bugs.
regards,
Rik
--
Bravely reimplemented by the knights who say "NIH".
http://www.surriel.com/ http://distro.conectiva.com/
Current spamtrap: <a href=mailto:"[email protected]">[email protected]</a>
> Count me in as a participant. One thing that would be nice is
> a mailing list where the bugs (and the changes to bugs) get
> mailed, so we can get updates by email.
Bugzilla has email triggers, so this should be dead easy to do.
Not sure if we need a list - bugzilla should be able to keep
each people's "watching" criteria itself. If it turns out lists
are easier, that should be easy to fix.
> I'll help track down, fix and admin bugs.
Thanks (to both of you ;-))!
M.
On Tue, 2002-10-22 at 02:43, Martin J. Bligh wrote:
> > Count me in as a participant. One thing that would be nice is
> > a mailing list where the bugs (and the changes to bugs) get
> > mailed, so we can get updates by email.
>
> Bugzilla has email triggers, so this should be dead easy to do.
> Not sure if we need a list - bugzilla should be able to keep
> each people's "watching" criteria itself. If it turns out lists
> are easier, that should be easy to fix.
>
> > I'll help track down, fix and admin bugs.
>
> Thanks (to both of you ;-))!
>From some good and bad experiences in the desktop universe - you need
people who are willing to collate bugs, sort them, tidy duplicates,
identify the most common bug report etc. Without that it doesn't work.
Watching what Luis did to the gnome bug reporting has been an education
but I don't think he can be cloned trivially and I don't think we could
run off with him 8)
Bug reporting systems need maintenance or they collapse
Alan Cox wrote:
> Bug reporting systems need maintenance or they collapse
Agreed, and IBM said that they would provide people doing this...
otherwise I would not have been so enthusiastic :)