Re: Bugzilla bug tracking database for 2.5 now available.

From: Brad Hards (
Date: Thu Nov 14 2002 - 22:46:44 EST

Hash: SHA1

On Fri, 15 Nov 2002 14:43, Thomas Molina wrote:
> My question is how should compile failures figure into the bug database?
> Most of the compile failures are typos or thinkos that get quickly fixed.
> Should they get tracked, or dismissed quickly unless they linger on. I
> didn't track simple compile failures in my list.
It probably depends where in the 2.5 cycle you are up to.

While there are still a lot of changes going in, it isn't so critical.

When it gets to 2.5.99 and later, you need to track absolutely everything.
Even if that means entering the problem, and 20 minutes later entering the
patch that corrects it, and the next day closing the bug against Linus' next

Given a resourced bug tracker, and the various test projects, this could be a
nice smooth release producing a product without gaping holes. But its
probably a bit soon to tell...


- -- 22-25Jan2003. Perth, Aust. I'm registered. Are you?
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

This archive was generated by hypermail 2b29 : Fri Nov 15 2002 - 22:00:35 EST