FYI...Thanks to this question, I've asked around and it looks like very few projects use the RTC model, and those projects use CTR for the trunk and RTC for backports where stability is paramount.
Having RTC for some portions of a project where it's important, and CTR for other parts is a rational policy. Especially since RTC by the formal definition requires a +3 vote for all code changes, which is a pretty significant hurdle.
How does this affect this discussion?1. RTC and CTR can coexist in the same project for different parts. Examples were contained in Gianugo's message yesterday: strong RTC (that is review + vote) required for specific subsets such as:
- API changes - backward-incompatible user-visible changes - backports to release branches - security fixes2. CTR can be modified to include a requirement for at least one review for significant changes.
3. Apache communities generally leave it up to the committers' discretion whether a change is significant enough to warrant review.
Craig On Aug 29, 2007, at 7:55 AM, Craig L Russell wrote:
Hi Bob, On Aug 29, 2007, at 7:25 AM, Bob Scheifler wrote:Craig L Russell wrote:I don't know of a project (here or elsewhere) that votes on code changes.Then why is it #1 on http://apache.org/foundation/voting.html?I believe that this page doesn't reflect current practice for most projects. I'll ask around and get a better answer.Thanks for following up. Craig- BobCraig Russell Architect, Sun Java Enterprise System http://java.sun.com/products/jdo 408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp!
Craig Russell Architect, Sun Java Enterprise System http://java.sun.com/products/jdo 408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp!
smime.p7s
Description: S/MIME cryptographic signature
