From: Chris Leonard <cjlhomeaddress@gmail.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: GLIBC bug list on sourceware.org
Date: Mon, 24 Oct 2016 19:48:00 -0000 [thread overview]
Message-ID: <CAHdAatYBoBkeTzVnqsgHyRg8VkSGA5C+tiZ89mLKgCKpSW7WBg@mail.gmail.com> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2016-10-24 19:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-20 19:36 Adhemerval Zanella
2016-10-24 19:48 ` Chris Leonard [this message]
2016-10-25 2:27 ` Siddhesh Poyarekar
2016-10-25 3:33 ` Carlos O'Donell
2016-10-30 4:01 ` Carlos O'Donell
2016-10-30 4:41 ` Andrew Pinski
2016-10-31 9:31 ` Carlos O'Donell
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=CAHdAatYBoBkeTzVnqsgHyRg8VkSGA5C+tiZ89mLKgCKpSW7WBg@mail.gmail.com \
--to=cjlhomeaddress@gmail.com \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).