tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Schultz <>
Subject Re: Invitation to become a Tomcat committer
Date Wed, 24 Nov 2010 15:05:20 GMT

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, did 'cd /www/ && 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?

>> Visiting the site doesn't seem
>> to reflect the change, though. Different server? Delay for worldwide
>> mirrors?
> people.a.o is not the public server. The content is rsync'd hourly to
> two servers - one in the US, one in the EU. Deletes are once per 24 hours.

Okay, good to know.

>> 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?

> 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)?

> Documentation is always CTR.
> For the releases using RTC there is a status file in the root of that
> part of the repo. Patches are added there and need at least 3 +1 votes
> (with no vetos) before they can be applied.
> BTW, it would have been fine to ask all of this on the dev list.



View raw message