On 24/11/2010 15:05, Christopher Schultz wrote: > Mark, > > On 11/23/2010 5:24 PM, Mark Thomas wrote: >> On 23/11/2010 22:10, Christopher Schultz wrote: >>> Done: I modified whoweare.xml, generated whoweare.html from that, >>> logged-into people.apache.org, did 'cd /www/tomcat.apache.org && scn up' >>> and saw the whoweare.html file updated. >> >> Hmm. I don't see the commit. Doh! I forgot to add your a.o e-mail to the >> dev allow list. Fixed. > > Okay, what do I do, now? svn says I have no differences in those files. > That is, my initial commit seems to have succeeded. Is my working copy > in some weird state, now?
No. It all worked. The only issue is that the commit e-mail that ws sent to the dev list is lost. It is possible to re-create it but I don't think it is worth it. If others disagree, I'll dig through the infra docs and remind myself how to do that. >>> On the other hand, I see a lot of stuff about proposing and nominating >>> patches, voting, etc. Is there some "howto" I can read for doing that, >>> or is it more of an etiquette that I just need to absorb from the others? >> >> tomcat/trunk is commit-then-review (CTR) > > Okay, so that means that commits happen and then anyone who wants to > review and/or complain is free to do so? Exactly. >> tomcat/site/trunk is CTR >> tomcat/tc6.0.x/trunk is review-then-commit (RTC) >> tomcat/tc5.5.x/trunk is RTC > > So the RTC policy is due to the "stable" nature of those branches, or > because they aren't seeing much in the way or new development (other > than backports from the 7.x branch)? The main reason those branches when to RTC was to reduce 'complications' when committers disagreed about what should go in those branches and/or how it should be implemented. RTC helps promote consensus. It does also aid stability. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
