Objective-C bugs and GCC releases

[Joe Buck]

On Tue, Jan 25, 2005 at 12:33:18PM -0700, Tom Tromey wrote:
> One potential problem I see with the current approach is that a
> non-release-critical language can be screwed by changes outside its
> purview.  For gcj we've occasionally had bugs (cf PR 19505) which
> occur in the gcc core.  In theory, something like this could be
> introduced the day before a release, and we'd end up shipping a broken
> gcj.  No amount of manpower can solve this.

We are not robots here; I know that Mark will use good judgment even if
not required to do so by what we have written down.  Should something like
that arise (a change goes in the last day that breaks Java, say), Mark can
still hold things up until the change is backed out or repaired.  However,
that can only happen if such things are caught quickly.