All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Adrian Bunk <bunk@kernel.org>
Cc: Natalie Protasevich <protasnb@gmail.com>,
	Bosko Radivojevic <bosko.radivojevic@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Number of bugs - statistics
Date: Fri, 23 May 2008 11:29:08 -0700	[thread overview]
Message-ID: <20080523112908.19f9413d@infradead.org> (raw)
In-Reply-To: <20080523165055.GC28257@cs181133002.pp.htv.fi>

On Fri, 23 May 2008 19:50:55 +0300
Adrian Bunk <bunk@kernel.org> wrote:

> On Fri, May 23, 2008 at 07:11:57AM -0700, Arjan van de Ven wrote:
> > On Fri, 23 May 2008 12:09:40 +0300
> > Adrian Bunk <bunk@kernel.org> wrote:
> > 
> > > 
> > > And in case anyone says "not forwarded distribution bugs aren't
> > > our problem":
> > > That's a nice example, since in this case a distribuion suddenly 
> > > starting to agressively forwarding their bugs might contribute to
> > > making the kernel better, but might also totally ruin the numbers
> > > in any statistics.
> > 
> > Fedora gets less than 1000 bugs per release (so 6 month window).
> > That's... peanuts.
> 
> 2000 kernel bugs per year?

it's going down; 750-ish for the last few releases

(see http://kernelslacker.livejournal.com/116718.html )
> 
> Then Fedora alone gets roughly as many kernel bugs as the kernel 
> Bugzilla.

but kernel bugzilla is "only" a last resort, while fedora bugzilla is a
first point of contact. I'd rate a kernel.org bugzilla bug to be 3x a
fedora bz bug in terms of value (eg less dupes, it's not support
requests but actual bugs etc etc).

> 
> >...
> > We are tracking over 3000 bugs per WEEK via other channels.
> >...
> 
> What exactly are you measuring with this "3000 bugs" number?

Oopses and places where the kernel goes WARN_ON().
(the oops:warning ratio is roughly 1:2 to 1:3)

  reply	other threads:[~2008-05-23 20:11 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-22 12:28 Number of bugs - statistics 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 [this message]
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
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=20080523112908.19f9413d@infradead.org \
    --to=arjan@infradead.org \
    --cc=bosko.radivojevic@gmail.com \
    --cc=bunk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=protasnb@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.