Jim Jagielski wrote:
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.
I don't see any difference with what happens at the moment, so since I think the current model has issues, it seems difficult for me to compromise on something even less than the ideas I just brought forward. I'll post a second vote eventually, and if it fails again, I think the Tomcat project should continue using the current model rather than come up with useless rules.
The main idea is that since there's only one trunk branch, there should be agreement on APIs and important topics to proceed, everything else should be in separate proposals. The mechanism also would work fine for release branches.
Rémy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
