From: Takashi Iwai <tiwai@suse.de>
To: James Courtier-Dutton <James@superbug.co.uk>
Cc: Adrian Bunk <bunk@kernel.org>,
Natalie Protasevich <protasnb@gmail.com>,
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: Fri, 23 May 2008 17:35:20 +0200 [thread overview]
Message-ID: <s5hzlqht4nb.wl%tiwai@suse.de> (raw)
In-Reply-To: <48369DD7.8040907@superbug.co.uk>
At Fri, 23 May 2008 13:35:03 +0300,
James Courtier-Dutton wrote:
>
> Adrian Bunk wrote:
> > On Thu, May 22, 2008 at 09:20:46AM -0700, Natalie Protasevich wrote:
> >
> >> On Thu, May 22, 2008 at 8:54 AM, Adrian Bunk <bunk@kernel.org> wrote:
> >>
> >>> 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.
> >>>
> >>>
> > Not everyone uses Bugzilla (e.g. ALSA uses Mantis).
> >
> > And the majority of bug reports might still go only to mailing lists and
> > not into any bugtracker at all. As long as this happens the data is
> > simply not available.
> >
> >
> >> by various criteria: ALSA bugs
> >> are numerous, which is not important for most enterprise server users
> >> who would completely disregard this category, whereas desktop users
> >> will probably concentrate on those more than any other.
> >>
> >
> >
> Although ALSA might have a lot of bug reports. Any bugs that affect
> kernel stability are fixed quickly.
> The rest of the ALSA bugs are more along the lines of "This feature on
> this particular sound card variant does not seem to work". This
> generally implies un-implemented features that uses now want. Some times
> the fix is simply adding that variant to the quirks list and finding out
> which quirk should be applied.
> So, once one removes the "un-implemented features" category from the
> ALSA bug list, one would expect the remaining number to be low.
... and a normal screening would reduce the amount of bugs to 1/4, I
guess. But, we have a serious problem regarding man power in this
area, unfortunately.
Takashi
next prev parent reply other threads:[~2008-05-23 15:35 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 [this message]
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=s5hzlqht4nb.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=James@superbug.co.uk \
--cc=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 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®