From: Carlos O'Donell <carlos@redhat.com>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>,
Adhemerval Zanella <adhemerval.zanella@linaro.org>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: GLIBC bug list on sourceware.org
Date: Tue, 25 Oct 2016 03:33:00 -0000 [thread overview]
Message-ID: <f6ff8c08-c825-751a-3bde-cc140f774b95@redhat.com> (raw)
In-Reply-To: <23dfa41a-12ea-533d-19a4-b4a05554d4d6@gotplt.org>
On 10/24/2016 10:27 PM, Siddhesh Poyarekar wrote:
> On Friday 21 October 2016 01:05 AM, Adhemerval Zanella wrote:
>> Another following idea is to also prioritize the bugs issues once the triage
>> is done.
>>
>> Any thoughts, ideas, advices?
>
> Carlos and I had talked about this in the past and we had agreed on
> using the release freeze time to try and bring the number of pending
> bugs down. We could try and make that idea into a more formal process,
> by making the slushy freeze time an official thing and encourage devs to
> work on reducing the bug backlog in that time.
>
> The trouble however is that very few contributors do glibc work full
> time and freezes are usually the time that they move on to do other
> things, unless they have pending patches or features that they care about.
We consciously choose a time-boxed release, and the consequence of that is
that we should be doing bug fixes in a continuous fashion.
I think we need some kind of weekly or monthly bug review which tries to
squash the bugs that have popped up.
https://sourceware.org/bugzilla/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=SUSPENDED&bug_status=WAITING&bug_status=REOPENED&f1=creation_ts&list_id=32518&o1=greaterthan&product=glibc&query_format=advanced&v1=2016-10-17
Last week we had 4 new bugs.
20729 glibc-2.24 fails to build for i486 with -Os
20728 powerpc: Missing TOC stub in clone
20720 ntfw with FTW_CHDIR and FTW_DEPTH can't back out of a tree properly giving ENOENT
20708 Extra test failures with LD_BNID_NOW=1
20707 gl_pathv entries not set to NULL with GLOB_DOOFFS
I'd focus on practicing a weekly triage of whatever was opened that week.
--
Cheers,
Carlos.
next prev parent reply other threads:[~2016-10-25 3:33 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
2016-10-25 2:27 ` Siddhesh Poyarekar
2016-10-25 3:33 ` Carlos O'Donell [this message]
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=f6ff8c08-c825-751a-3bde-cc140f774b95@redhat.com \
--to=carlos@redhat.com \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.org \
--cc=siddhesh@gotplt.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).