This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: your RESOLVED->CLOSED changes
- From: Wolfgang Bangerth <bangerth at ices dot utexas dot edu>
- To: "John Anthony Kazos Jr." <jkazos at vt dot edu>
- Cc: gcc at gcc dot gnu dot org
- Date: Fri, 23 May 2003 09:45:16 -0500 (CDT)
- Subject: Re: your RESOLVED->CLOSED changes
>> I would also like to posit that quite a number of bugs will then stay
>> RESOLVED indefinitely. If someone, say, fixes a bug on mn10200 or some
>> other obscure target, who's going to double-check after a release and
>> put in into CLOSED?
>
> Doesn't that prove the lack of QA, and demonstrate the need for it? If a
> fix hasn't been checked, it *should* remain resolved-but-unclosed
> indefinately until someone checks it. Otherwise, why bother checking
> fixes at all?
Yes and no. Yes, because in a sense you're right but it's just a fact that
we're developer starved and don't have enough people working on the rarer
platforms.
No, since at least in principle each patch should go in with a testcase,
so the very same developer will re-check every time he runs the testsuite.
The initial check whether a patch is sane is done by peer review.
W.
-------------------------------------------------------------------------
Wolfgang Bangerth email: bangerth@ices.utexas.edu
www: http://www.ices.utexas.edu/~bangerth/