mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Jesper Juhl <jesper.juhl@gmail.com>,
	Linus Torvalds <torvalds@osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Adrian Bunk <bunk@stusta.de>
Subject: Re: A proposal; making 2.6.20 a bugfix only version.
Date: Thu, 09 Nov 2006 10:52:00 +0100	[thread overview]
Message-ID: <1163065920.3138.486.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20061109013645.7bef848d.akpm@osdl.org>


> 
> 70% hit a bug

this part I consider meaningless personally. If it was "70% hit a
regression" or even x% hit a regression I would be a lot more worried.

> 1/7th think it's deteriorating
> 1/4th think lkml response is inadequate
> 3/5ths think bugzilla response is inadequate
> 2/5ths think we have features-vs-stability wrong
after lots of press. 
> 2/3rds hit a bug.  Of those, 1/3rd remain unfixed
> 1/5th of users are presently impacted by a kernel bug
> 
> Happy with that?

I'm not saying things are perfect. Far from that.
What I care about is if things are getting worse or not. My personal
impression is that while things were flakey on the ABI front during
early 2.6 (before 2.6.12 or so), that got fixed because every single bug
is a major annoyance to a large group of people. (and most bugs in the
survey were from before that).

The counter argument to your "doom" data is that bugrates for acpi for
example have been mostly steady, while the number of users has been
increasing quite a bit. 

I don't have the impression things are getting worse personally. I do
hit bugs, in -mm and in -rc kernels, but that is because I'm testing
kernels intended for testing. (another thing that the 70% figure didn't
separate out)

We've gotten better. Adrian started tracking regressions, and that is
helping to make sure that those don't slip through the cracks as much as
they used to (some are unavoidable, especially performance ones or ones
with really obscure hardware that is showing hard to reproduce things).
The -stable series is working out well to fix security and other
annoying bugs quickly post release (because yes things don't get tested
fully until you release), but even -stable is not nearly getting massive
infloods of serious regressions. Sure they are fixing more stuff now,
but that's more a sign that the process is working, and that they are
now picking up less critical stuff as well, than that it is a sign that
things are getting worse.

I'd love if bug responses were better. At the same time, declaring
"bugfix only kernel" isn't going to improve that much; it just creates a
larger flood of stuff for the kernel after that. Do you have the
impression that high quality bug reports on lkml (with this I mean ones
where there is sufficient information, which are not a request for
support and where the reporter actually answers questions that are asked
him) are not getting reasonable attention? 

 
-- 
if you want to mail me at work (you don't), use arjan (at) linux.intel.com
Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org


  reply	other threads:[~2006-11-09  9:52 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-08 22:09 Jesper Juhl
2006-11-08 22:22 ` Arjan van de Ven
2006-11-08 22:40   ` Jesper Juhl
2006-11-08 23:05     ` Andreas Mohr
2006-11-08 23:54       ` Jan Engelhardt
2006-11-10 15:15     ` Pavel Machek
2006-11-10 15:48     ` Horst H. von Brand
2006-11-15 21:04       ` Jesper Juhl
2006-11-08 22:51   ` Andrew Morton
2006-11-09  9:26     ` Arjan van de Ven
2006-11-09  9:36       ` Andrew Morton
2006-11-09  9:52         ` Arjan van de Ven [this message]
2006-11-09 19:12           ` Andrew Morton
2006-11-09 19:21             ` Arjan van de Ven
2006-11-09 21:11               ` Adrian Bunk
2006-11-09 21:31                 ` Arjan van de Ven
2006-11-09 23:56                   ` Thomas Gleixner
2006-11-10  0:18                     ` Andrew Morton
2006-11-10 17:45                     ` Stefan Richter
2006-11-11 11:00                     ` Martin J. Bligh
2006-11-08 23:28   ` Diego Calleja
2006-11-09  6:48     ` Arjan van de Ven
2006-11-09 12:45       ` Rolf Eike Beer
2006-11-09  4:57 Al Boldi
2006-11-09 17:05 ` Stephen Hemminger
2006-11-10 15:52   ` Al Boldi
2006-11-10 16:16     ` Jesper Juhl
2006-11-10 16:42       ` Stephen Hemminger
2006-11-10 16:53         ` Randy Dunlap
2006-11-10 19:33           ` Al Boldi
2006-11-10 19:49             ` Arjan van de Ven
2006-11-10 21:22               ` Al Boldi
2006-11-10 21:31                 ` Stephen Hemminger
2006-11-11  4:15                   ` Al Boldi
2006-11-11  5:09                     ` Stephen Hemminger
2006-11-11  7:23                       ` David Miller
2006-11-11 11:15                         ` Al Boldi
2006-11-11  6:31                     ` Valdis.Kletnieks
2006-11-11 11:15                       ` Al Boldi
2006-11-11  7:15           ` Willy Tarreau
2006-11-11 12:03             ` Neil Brown
2006-11-11 19:16           ` Krzysztof Halasa
2006-11-11 19:15         ` Adrian Bunk

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=1163065920.3138.486.camel@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --cc=akpm@osdl.org \
    --cc=bunk@stusta.de \
    --cc=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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

all inboxes | Powered by JetHome®