This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: GLIBC bug list on sourceware.org
- From: Chris Leonard <cjlhomeaddress at gmail dot com>
- To: Adhemerval Zanella <adhemerval dot zanella at linaro dot org>
- Cc: GNU C Library <libc-alpha at sourceware dot org>
- Date: Mon, 24 Oct 2016 15:47:19 -0400
- Subject: Re: GLIBC bug list on sourceware.org
- Authentication-results: sourceware.org; auth=none
- References: <df0726b2-eb44-1c2f-cf0f-9dc1862230b8@linaro.org>
On Thu, Oct 20, 2016 at 3:35 PM, Adhemerval Zanella
<adhemerval.zanella@linaro.org> wrote:
> Hi all,
>
> As Joseph has pointed out earlier in IRC, sourceware.og just surpassed
> 1000 registered bugs [1]. And this list only increases over time.
>
> I cracked down by category and current list (when this mail was crafted,
> Oct-20) is:
>
> Component # Bugs
> localedata 93
>
> Also, as Joseph has commented on IRC and I agree with him, the expectation is
> that fewer than half the bugs are actually genuine issues that are hard to fix;
> maybe fewer than 200. There are lots that should be easy to fix (or easy for
> someone familiar with the relevant architecture, in some cases), and probably
> a fair number that are really feature requests that need consensus to be
> reached.
>
> So I think a initial triage to check for actual bugs with some ping to get
> consensus can help on get this under control. My idea is to use this thread
> to reference bugs that might not be real issues to ask for a second look and
> thus close them.
>
> Another following idea is to also prioritize the bugs issues once the triage
> is done.
>
> Any thoughts, ideas, advices?
I'd love to help work on the localedata tickets. Some of them are
actually mine (new locales). I've tried posting some patches to the
list, but have encountered challenges as posts are apparently tripping
a spam filter.
cjl