Re: GCC 3.3, GCC 3.4

[Devang Patel <dpatel at apple dot com>]

On Friday, January 31, 2003, at 10:57 AM, Mark Mitchell wrote:

> From: Mark Mitchell <mark@codesourcery.com>
> Date: Fri Jan 31, 2003  10:57:48 AM US/Pacific
> To: Devang Patel <dpatel@apple.com>
> Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
> Subject: Re: GCC 3.3, GCC 3.4
>
>
>
> --On Friday, January 31, 2003 09:54:49 AM -0800 Devang Patel 
> <dpatel@apple.com> wrote:
>
> > > If people have concerns about how I'm doing my job, I want to hear
> > > them.
> > I really appreciate what you're doing, but (:-)) GCC project will
> > benefit more if you become little be more strict about regressions.
> I agree with most of what you say, including this.  Would Apple care
> to donate some time/resources for you to set up a machine with more
> automated testing?  (Obviously, we'd be happy to help, if anyone wants
> to outsource this kind of thing as well.)
I think Geoff has already setup darwin-ppc regression tester.

But we need to find ways to stop regressions so that we do not have to 
lots of
spend time and resources to find and fix them.

I'm thinking - "Can we check regression before commits?". Can we have
setup to queue all incoming commits and churn it through regression 
testing
machinery before actually committing it?. I do not know if this is 
possible or
not, but it would be great.

> We do have a policy
> to deal with regressions -- but we almost never use it.  I don't know
> that we want to be too agressive, but maybe we should be a little more.

> You can help!  When you spot a regression, mention it to the person
> who caused it, post to the list, and notify me.
I will. Janis and Wolfgang and other people are doing really great job
in finding regressions. But it is disappointing that we have not done
much to help them. Wolfgang reported that he has encountered couple of
regressions that stop him building his library since last 6 weeks or so.

-Devang