Re: bug tracking

From: Adrian Bunk
Date: Wed Jan 18 2006 - 03:05:54 EST


On Tue, Jan 17, 2006 at 03:50:13PM -0800, Andrew Morton wrote:
>...
> So please don't let me discourage you from doing this - if a reporter gets
> multiple emails regarding a bug, he's unlikely to be offended - it's heaps
> better than zero emails! I'll cc you in future if you like so we can avoid
> duplication.

You can Cc me, but there might be other people with the same problem.

But thinking about it, the real issue seems to be that the Linux kernel
is the only open source project of this size I know about where bug
reporters are not encouraged to enter all bugs in a bug tracking system
resulting in manual work to track them.

There are classes of bugs where Bugzilla doesn't bring much ("your patch
xyz.patch in the latest -mm breaks compilation on i386"), but for most
bug reports it would be nice. The problem is that while some subsystem
maintainers use the kernel Bugzilla, others don't want to use it and
want bug reports sent to mailing lists instead.

I know that some kernel developers do not like Bugzilla, but the kernel
Bugzilla has email interfaces in both directions and it should therefore
be possible to integrate into existing workflows without too much
overhead.

This way, the bookkeeping of bugs is done automatically, and although
this does not automatically fix bugs I've e.g. had some cases where I
told maintainers "please review your 19 open bugs in the kernel
Bugzilla" resulting in maintainers actually reviewing and fixing bugs.
This included cases where the old maintainer was inactive and a new
maintainer has taken over maintainership.

How can we get to the state that there's a kernel bug tracking system
every maintainer is using?

cu
Adrian

--

"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/