From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 117076 invoked by alias); 24 Oct 2016 19:48:18 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 117057 invoked by uid 89); 24 Oct 2016 19:48:17 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.8 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=no version=3.3.2 spammy=challenges, familiar, love, him X-HELO: mail-qk0-f181.google.com X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=5yaBWnTee01F4LycLJNc79iyqmMH8IiCDdzODw0Ig08=; b=dHWtzYWFWCMvF+8uEH9Aa4AsmodtuHvr03InJKEHCmveZhg7OYB+QUjLCQm+NFENy6 lFtCLxKMD8IC+U938WW/Rjfo09+8OonZGLVkYlR2ziuyuPslZvPA6MJt7ykPayU47295 QXSBGq7AgIOqh+ThSuJIJuw9nPDI9OCmjF0VhflEcfaMlH//nmrflhFzjXd7wSb5fQ2F LczF4Dpsao9TyubEo2sMYN/Om238cHWXVRvrpSf9IxxYgcKKT/9ArCZF8mUDpPcnvSM2 KGYKPawspJlZiYGAp8DiFqNdkIDqXb/4RJ2zbCo2HyUCBHclqbGQUkGZJ5c/giy79OJ0 bj8Q== X-Gm-Message-State: ABUngvdk74lXbmI0dZ+HP4M15btnhhxrM2oa/ydY90dr/fqWtgSwFD2K75xXDXaBKZNx4FiC3lN36SFoiaIlYQ== X-Received: by 10.55.209.150 with SMTP id o22mr8893425qkl.274.1477338479790; Mon, 24 Oct 2016 12:47:59 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: From: Chris Leonard Date: Mon, 24 Oct 2016 19:48:00 -0000 Message-ID: Subject: Re: GLIBC bug list on sourceware.org To: Adhemerval Zanella Cc: GNU C Library Content-Type: text/plain; charset=UTF-8 X-SW-Source: 2016-10/txt/msg00403.txt.bz2 On Thu, Oct 20, 2016 at 3:35 PM, Adhemerval Zanella 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