This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Bug tracking / Release Quality Assurance
- From: Volker Reichelt <reichelt at igpm dot rwth-aachen dot de>
- To: gcc at gcc dot gnu dot org, pfeifer at dbai dot tuwien dot ac dot at
- Cc: mark at codesourcery dot com, nathan at codesourcery dot com
- Date: Mon, 9 Dec 2002 20:08:52 +0100
- Subject: Re: Bug tracking / Release Quality Assurance
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