This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: More bug fixing needed
- From: Andreas Jaeger <aj at suse dot com>
- To: libc-alpha at sourceware dot org
- Date: Mon, 03 Sep 2012 10:20:22 +0200
- Subject: Re: More bug fixing needed
- References: <Pine.LNX.4.64.1208301143200.9433@digraph.polyomino.org.uk> <503F73A8.4020304@systemhalted.org> <Pine.LNX.4.64.1208301420380.11684@digraph.polyomino.org.uk>
On Thursday, August 30, 2012 14:28:21 Joseph S. Myers wrote:
> On Thu, 30 Aug 2012, Carlos O'Donell wrote:
> > One thing we might do is have a bug triage day and time. Say
> > Thursday afternoon we get together on IRC at a particular time and
> > do a group triage, talk about the bugs and work through N bugs in
> > 30 minutes.
> >
> > I think this would help get us into the habit of doing triage.
> >
> > Comments?
>
> I guess triage might reduce the open bugs by 10% or so, by identifying
> bugs that have in fact been fixed (with or without reference to the
> bug number in the ChangeLog) but not closed as such, bugs where we
I expect that there are few already fixed bugs in bugzilla, I went
through nearly all bugs and checked them - but still errors can happen.
> can conclude that the report is mistaken or the requested change not
> desirable, and bugs that lack sufficient information to confirm or
> reproduce them and where this was noted a while back without response
> from the submitter (whether or not explicitly in WAITING state).
For these kind of bug reports, an IRC session would help a lot.
> There may also be some bugs with patches attached that can go in more
> or less as is (no copyright assignment issues, no need for extra
> testcases, etc.) and just need retesting and submitting to
> libc-alpha. And triage can also help confirm bugs that may not have
> clear testcases or conclusions about whether they are valid.
Yes.
> But where a bug needs a patch to be written to fix it, that fixing
> (complete with testsuite additions and writing up the bug and the
> approach taken to fix it) is unlikely to be possible within 30
> minutes; I generally expect even pretty straightforward bugs to take
> longer than that to complete fixing.
Indeed - still coordination on how to tackle a bug might be a nice idea.
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126