How about:
o CTR on trunk
o Various release branches are made (ala httpd, apr, etc...).
These include a STATUS file.
o All code applied to the release branch is under
lazy consensus but *must* be specified in STATUS.
(eg: "I plan on applying rev786987 in 3 days under
lazy consensus").
Not as stringent as RTC, but also provides a good level
of oversight with a minimum of overhead... RTC can be
maintained for older, stable releases.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
