RE: GCC 4.2.0 Status Report (2007-04-15)

[Eric Weddington <eweddington at cso dot atmel dot com>]

> -----Original Message-----
> From: Mark Mitchell [mailto:mark@codesourcery.com] 
> Sent: Sunday, April 15, 2007 4:51 PM
> To: GCC
> Subject: GCC 4.2.0 Status Report (2007-04-15)
> 
> However, I would consider asking the SC for permission to institute a
> rule that would prevent contributors responsible for P1 bugs (in the
> only possible bright-line sense: that the bug appeared as a result of
> their patch) from checking in changes on mainline until the P1 bug was
> resolved.  This would provide an individual incentive for 
> each of us to
> clean up our own mess.  I'm certain that someone will raise 
> the "latent
> bug" issue, but that's not the common case.  And, we can always decide
> to make an exception if necessary.  Of course, if we do this, I'd be
> happy to recuse myself as necessary, in order to avoid any 
> appearance of
> favoritism towards CodeSourcery personnel.
> 
> What do people think of that suggestion?

Instead of creating a new rule to try to convince people to get things done,
why not use your role of release manager and just not allow a release of 4.2
or 4.3 until the quality is deemed sufficient. If it takes longer to do a
release then so be it. Politely point out what is left to get done. The
status reports are a helpful reminder of the state of the branch.

Eric Weddington