This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
bug management: WAITING bugs that have timed out
- From: Joe Buck <Joe dot Buck at synopsys dot COM>
- To: gcc at gcc dot gnu dot org
- Date: Thu, 11 Jan 2007 22:47:15 -0800
- Subject: bug management: WAITING bugs that have timed out
Hi,
http://gcc.gnu.org/bugs/management.html says that bugs in WAITING
state for more than three months, waiting for information on how
to reproduce the bug, can be closed, but it is unclear what the
"closed" state should be.
The description of WORKSFORME sounds closest: we don't know how to
reproduce the bug. Should that be used? The only other choices
are FIXED (wrong), DUPLICATE (wrong), INVALID (we don't know that),
or WONTFIX (we're not saying we won't fix it if we get a testcase).
This came up because RMS raised a concern about the large number
of wrong-code bugs; many of those not marked "regression" are WAITING,
or should be WAITING. I'd like to knock off a few (and of course
they can be re-opened if we get more data).