Re: Power of the G++ test suite

[Carlo Wood <carlo at runaway dot xs4all dot nl>]

Mark Mitchell wrote:
|                                                       I save every bug
| report, so, at some point, I'll probably get around to fixing the bug,
| if someone else doesn't.

Thats cool :)

[...]
| In summary, I suspect that if you calm down and wait patiently, your
| test case will indeed be added to the test suite.

Ok, I will be patient ;).  

I don't have any problem with it not being added anyway, I just wondered
WHY it wasn't added.

Maybe a bug(-report) tracking system would help, I see lots of people
who report bugs and get disappointed when they never hear anything
again...  A webpage that allows them to find back their report and
its status might motivate them to contribute more in the future, while
it will make coordination of pending bugs and fixes easier.

The following statuses seem reasonable:

1) Received (automated)
2) Format approved
   or
   Send back to sender with request to conform to <url>
   (ie minimize the code; make it standalone/reproducable etc).
3) Confirmed to fail
   or
   Doesn't fail with version/environment ... (mail back to sender)
4) Confirmed to be a real, new bug
   or
   Closed: not a bug because <reference to standard>
5) Confirmed not to overlap with existing tests
   or
   Closed: Identical with ...
6) Code minimized
7) Being fixed by ...
8) Fixed <url to patch>

Of course it should be garanteed that every bug report is
handled, and thus a priority system should be set up which
determines what needs to be done next.  This priority system
could depend on date of submission and a 'urgency tag' that
is assigned during phase 3) for instance.

$0.02,

-- 
 Carlo Wood  <carlo@runaway.xs4all.nl>