mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@kernel.org>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Arjan van de Ven <arjan@infradead.org>,
	Bosko Radivojevic <bosko.radivojevic@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Number of bugs - statistics
Date: Thu, 22 May 2008 20:09:56 +0300	[thread overview]
Message-ID: <20080522170956.GC2727@cs181133002.pp.htv.fi> (raw)
In-Reply-To: <48359DE1.8050600@s5r6.in-berlin.de>

On Thu, May 22, 2008 at 06:22:57PM +0200, Stefan Richter wrote:
> Adrian Bunk wrote:
> > On Thu, May 22, 2008 at 07:51:35AM -0700, Arjan van de Ven wrote:
> >> Maybe some other data:
> >> * The incoming rate of ACPI bugs has been pretty much flat the last 3
> >> years, while the number of Linux (and ACPI) users has grown
> >> significantly. The number of unfixed bugs has more than halved, from
> >> over 200 to well below 100.
> >> * The SCSI maintainer also reports that he sees flat to declining bug
> >> rates; again with the increase in Linux user base that is a good sign
> > 
> > Andrew sees and handles the majority of incoming bug reports.
> > Ask him whether he agress with this.
> > 
> > And ALSA alone has 2000 open bug reports, which makes the open ACPI or 
> > SCSI bug numbers relatively irrelevant in any "number of bugs" 
> > statistics.
> 
> Central facilities like ACPI and SCSI having relatively few [and
> according to Arjan a decreasing number of] reported unfixed bugs is...
> irrelevant?

Yes, _in any "number of bugs" statistics_ that is irrelevant.

You seem to confuse "number of bugs" with "stability".
As Arjan often emphasizes this is wrong.

We do not even have good data for "number of bug reports".
And getting data for "stability" would be a quite hard task.

> Stefan Richter

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


  parent reply	other threads:[~2008-05-22 17:12 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-22 12:28 Bosko Radivojevic
2008-05-22 14:41 ` Adrian Bunk
2008-05-22 14:51   ` Arjan van de Ven
2008-05-22 15:47     ` Natalie Protasevich
2008-05-22 15:54     ` Adrian Bunk
2008-05-22 16:20       ` Natalie Protasevich
2008-05-22 16:50         ` Adrian Bunk
2008-05-22 17:08           ` Natalie Protasevich
2008-05-22 17:33             ` Adrian Bunk
2008-05-22 17:51               ` Natalie Protasevich
2008-05-22 18:11                 ` Adrian Bunk
2008-05-22 22:18           ` Arjan van de Ven
2008-05-23  9:09             ` Adrian Bunk
2008-05-23 14:11               ` Arjan van de Ven
2008-05-23 16:50                 ` Adrian Bunk
2008-05-23 18:29                   ` Arjan van de Ven
2008-05-23 20:31                     ` Adrian Bunk
2008-05-26 17:05                       ` Dave Jones
2008-05-23 10:35           ` James Courtier-Dutton
2008-05-23 15:35             ` Takashi Iwai
2008-05-22 16:22       ` Stefan Richter
2008-05-22 16:38         ` Bart Van Assche
2008-05-22 17:09         ` Adrian Bunk [this message]
2008-05-22 17:45           ` Stefan Richter
2008-05-22 19:17             ` 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=20080522170956.GC2727@cs181133002.pp.htv.fi \
    --to=bunk@kernel.org \
    --cc=arjan@infradead.org \
    --cc=bosko.radivojevic@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stefanr@s5r6.in-berlin.de \
    /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®