From: Volker Reichelt <reichelt@igpm.rwth-aachen.de>
To: gcc@gcc.gnu.org, pfeifer@dbai.tuwien.ac.at
Cc: mark@codesourcery.com, nathan@codesourcery.com
Subject: Re: Bug tracking / Release Quality Assurance
Date: Mon, 09 Dec 2002 10:14:00 -0000 [thread overview]
Message-ID: <200212091908.UAA35148@numa6.igpm.rwth-aachen.de> (raw)
There are about 30 bugs in feedback state where no feedback was received
for more than 6 months. An additonal 20 reports got no feedback for 3
months.
Most of these bugs aren't missing crucial information (like a
preprocessed file), but are left in an inconclusive state about what
action to take.
I don't think they should be closed unconditionally, but should be
revisited. Maybe their state should be changed to "open" in some cases.
We could try to ping the respective developers, about what to do.
When adding an entry for the policies section of gnatswrite.html,
I would suggest closing only those PRs after 3 months that lack crucial
parts of information (like a preprocessed file) that hinder analysis.
Regards,
Volker
next reply other threads:[~2002-12-09 18:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-09 10:14 Volker Reichelt [this message]
2002-12-09 10:42 ` Mark Mitchell
-- strict thread matches above, loose matches on Subject: below --
2002-10-10 8:01 Nathanael Nerode
2002-10-08 7:31 Roger Sayle
2002-10-08 8:53 ` Neil Booth
2002-10-08 8:59 ` Roger Sayle
2002-10-07 9:38 Gerald Pfeifer
2002-10-07 9:42 ` David S. Miller
2002-10-07 10:26 ` Jakub Jelinek
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-10-08 0:43 ` Gabriel Dos Reis
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=200212091908.UAA35148@numa6.igpm.rwth-aachen.de \
--to=reichelt@igpm.rwth-aachen.de \
--cc=gcc@gcc.gnu.org \
--cc=mark@codesourcery.com \
--cc=nathan@codesourcery.com \
--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).