From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 111679 invoked by alias); 20 Oct 2016 19:36:04 -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 111632 invoked by uid 89); 20 Oct 2016 19:36:03 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=no version=3.3.2 spammy=list_id, nis, cracked, him X-HELO: mail-vk0-f47.google.com X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding; bh=uhP7aA/zPBPR4PSslPb/rz8/9KMuomiPcI0LNAznmzI=; b=a1/VsSh1DKG5a1lIdDXSNBUaEwvgY/PPWwVfN+lRIzKY1YKlydi8YO6M8cH33zszEJ V5ropleE3Ol3/lNt03XUWqHPyRYvXIUJBjMxDBeVJVC59aWrI86n4TYD5+42wMhUPDoc VvxBlRzxsdwRR+G5h/v95cnnU4x+D6PkW23x62aK1o7IgSPL+3fYIA6uSj/Jr4wdwsdl YOPaFU9kJeC5mWpvjhGZE1HddLVnvc3zxkq5ecpaSzwLUqnrei08FLpOozf3j8O3T8/s aw9qDA/R8pzNI6dNpqG5d15c0NscgERayFuhe0zguUk4NrBARYmJxBCWHWCMuI9i/0fH LsoQ== X-Gm-Message-State: AA6/9RnEc7LxIKJiPYD9y/rc0oAUWJf5F7aPNUdd4Kwuq2hzHjdqqaSXuH/pV8g6GuXPKJUk X-Received: by 10.31.9.210 with SMTP id 201mr3623769vkj.106.1476992151742; Thu, 20 Oct 2016 12:35:51 -0700 (PDT) To: GNU C Library From: Adhemerval Zanella Subject: GLIBC bug list on sourceware.org Message-ID: Date: Thu, 20 Oct 2016 19:36:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-SW-Source: 2016-10/txt/msg00343.txt.bz2 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 libc 220 dynamic-link 96 network 94 localedata 93 nptl 79 manual 55 locale 52 build 46 stdio 45 math 43 malloc 33 string 26 regex 24 time 24 nscd 18 librt 12 glob 11 nss 11 admin 7 hurd 4 nis 4 soft-fp 2 buildbot 1 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? [1] https://sourceware.org/bugzilla/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=SUSPENDED&bug_status=WAITING&bug_status=REOPENED&limit=0&list_id=32453&order=component%2Cchangeddate%2Cproduct%20DESC%2Cbug_id%20DESC&product=glibc&query_format=advanced