public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: "David S. Miller" <davem@redhat.com>
Cc: pfeifer@dbai.tuwien.ac.at, gcc@gcc.gnu.org
Subject: Re: Bug tracking / Release Quality Assurance
Date: Mon, 07 Oct 2002 10:26:00 -0000	[thread overview]
Message-ID: <20021007182645.I3451@sunsite.ms.mff.cuni.cz> (raw)
In-Reply-To: <20021007.091205.37591802.davem@redhat.com>; from davem@redhat.com on Mon, Oct 07, 2002 at 09:12:05AM -0700

On Mon, Oct 07, 2002 at 09:12:05AM -0700, David S. Miller wrote:
>    From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
>    Date: Mon, 7 Oct 2002 18:03:28 +0200 (CEST)
> 
>    1. I believe we should not ship GCC 3.2.1 (or branch 3.3.) until this
>       bug count has been significantly reduce.
>    
>    2. I suggest that we close PRs that have been in feedback state but
>       not received any response for more than 6 months:
>    
>       Examples: 3931, 4650, 5971, 5515, 6545
>    
>    3. We probably need some (further) volunteers who monitor GNATS more
>       closely, ask submitters for further information/feedback and ping
>       maintainers concerning problems in their areas.
> 
> I agree on #1 and #2, but I'm not so sure #3 is going to help
> all that much.
> 
> If maintainers aren't finding enough time to monitor GNATS in their
> particular area, it is likely they are overloaded enough that some
> volunteer pinging them they have stuff to look at won't get it done.
> 
> The volunteer who does the "ask for more information" bit will need
> to be quite knowledgable.  But if you found such a person who isn't
> already taxed with GCC things to do, it would be useful to have
> them help in this area.

A lot of GNATS bugreports come with huge testcases. Trimming them into
testcases suitable for gcc testsuite (and at the same time into a size
in which they can be easily debugged) and where easily possible figuring
roughly what the bug area is would surely help IMNSHO.

	Jakub

  reply	other threads:[~2002-10-07 16:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-07  9:38 Gerald Pfeifer
2002-10-07  9:42 ` David S. Miller
2002-10-07 10:26   ` Jakub Jelinek [this message]
2002-10-07  9:50 ` Nathan Sidwell
2002-10-08 12:38   ` Mark Mitchell
2002-10-08 16:07     ` Pop Sébastian
2002-12-07  6:53   ` Gerald Pfeifer
2002-12-08 19:16     ` Mark Mitchell
2002-12-09 10:06       ` PATCH for " Gerald Pfeifer
2002-10-08  0:43 ` Gabriel Dos Reis
2002-10-08  7:31 Roger Sayle
2002-10-08  8:53 ` Neil Booth
2002-10-08  8:59   ` Roger Sayle
2002-10-10  8:01 Nathanael Nerode
2002-12-09 10:14 Volker Reichelt
2002-12-09 10:42 ` Mark Mitchell

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=20021007182645.I3451@sunsite.ms.mff.cuni.cz \
    --to=jakub@redhat.com \
    --cc=davem@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=pfeifer@dbai.tuwien.ac.at \
    /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).