Re: regression hunt status, question about reports to mailing list

[Janis Johnson <janis187 at us dot ibm dot com>]

On Fri, Dec 20, 2002 at 11:27:07AM -0600, Wolfgang Bangerth wrote:
> 
> (Janis wrote:)
> > Should I continue to send mail to gcc@gcc.gnu.org when I identify the
> > patch that caused a regression or that fixed a mainline regression that
> > still exists on a release branch?  This seemed like a good idea when
> > there was one every couple of days, but I'm continuing to discover
> > short-cuts that make it faster and easier, so the trickle of mail might
> > be getting large enough to be annoying
> 
> I think you should. I guess, some nagging is ok, after all we haven't seen 
> a rush to fix the regressions for which the offending patch has been 
> identified. Yesterday, we had 90 (!) listed regressions, and little 
> movement to get them fixed (except for Eric's noticable work on the 
> optimization bugs). A little public pressure seems appropriate.

The people I've notified are all very active contributors to GCC, and it
doesn't surprise me that they haven't fixed the regressions immediately.
I don't expect them to need nagging, but we should certainly remind them
about remaining regressions when we get close to deadlines.  It's also
quite possible that the people who fix the bugs will not be the ones
whose patches caused them to show up.

Janis