your RESOLVED->CLOSED changes
Wolfgang Bangerth
bangerth@ices.utexas.edu
Fri May 23 19:23:00 GMT 2003
> > 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?
>
> Yup. Well, me, but other than that. :-)
But that's the whole point. We got into the problem of having 2000 open
reports at one point in time exactly because those people with obscure
platforms didn't check into the database. I see no reason to believe that
this has changed. If we ask them to do that, nothing's going to happen and
these PRs will stay in VERIFIED forever. Let's just be pragmatic and say
that we don't have the resources to do anything better than our testsuite,
and let's drop 2 of the 3 states. If at one point we have the resources,
we can still add it again and start to use it with release N+1.
W.
-------------------------------------------------------------------------
Wolfgang Bangerth email: bangerth@ices.utexas.edu
www: http://www.ices.utexas.edu/~bangerth/
More information about the Gcc
mailing list