Share your designs before you implement, consider your impact on the
greater whole, ask questions, think it through. Test before you land,
and test again. We've seen examples of how huge changes, with some
planning and coordination, can be done with success. It's all about
executing on the fundamentals.
Andrew Huntwork wrote:
>
> Come on Blake, this is too easy: If no one checks anything in there
> can't be any regressions. :) So just add another couple levels of approval.
>
> You could also filter your bugzilla mail to the trash...(Unless the
> regression is in mail filters of course)
>
> Blake Ross wrote:
>
> > Lately I've been flooded with notifications of regressions -- not
> > necessarily in core features, but just all over the product. Anyone else
> > feel that way? Anything we can do to improve the situation?
> >
> > --Blake
> >
> >
> >
--
Syd Logan
Unix Software Engineer
Netscape, Communications - a division of AOL.
