Re: Bug#265831: Obsolete bugreports for 2.4
On Fri, Oct 27, 2006 at 08:46:00PM -0700, Steve Langasek wrote:
>
> On Fri, Oct 27, 2006 at 01:23:31PM +0200, David Schmitt wrote:
> > This bugreport contains a report of problems with the 2.4 kernel. This version
> > will not be shipped with etch, therefor I close this report retrospectively
> > for version 2.6.0.
>
> This is not an appropriate way to handle a bug report. This bug was
> explicitly reassigned to the linux-2.6 package because it was still
> relevant. The nature of the bug is such that you don't even have to have
> particular hardware to verify whether it's present, all you have to do is
> look at the source package to see whether the config option is set. If you
> can't be bothered to do that, you should not be closing bug reports. Not
> that closing a bug with a non-existant "2.6.0" version actually has the
> intended effect...
>
> As it happens, this particular bug is fixed, but only as of version
> 2.6.15-7.
Hi David,
I just wanted to tell you how much I appreciate the work you are doing
on kernel bugs. It seems like these days nobody on the team has time
left over to do any serious bug tracking, especially deal with the
bugs which are sitting in the BTS forever. I hope you will not be
discouraged by Steve's note. Besides being the kernel team member,
he's also the one wearing the release manager hat, and the correct
version tracking information is especially important for the release
team. Whenever you feel uncertain on what's the best way to handle a
particular bug, I would be glad to discuss the best strategy with you,
either on the d-k list, or in private. And we can always bug Steve for
some guidance in pathological cases :-).
Once again, thanks for your efforts.
--
Jurij Smakov jurij@wooyd.org
Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC
Reply to: