trafficserver-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bryan Call <bc...@yahoo-inc.com>
Subject Re: [vote] RTC vs CTR
Date Tue, 02 Mar 2010 17:03:09 GMT
I was able to see both messages on the list from you...

-Bryan

On 03/02/2010 08:54 AM, John Plevyak wrote:
> I think I am having trouble getting my messages to the list,
> so I am sending this from a different address as a test, sorry
> for the duplication.
>
> [+1] CTR for trunk, RTC for all release branches
>
> john
>
>
> On 3/1/2010 8:52 PM, Paul Querna wrote:
>    
>> On Mon, Mar 1, 2010 at 7:44 PM, Leif Hedstrom<zwoop@apache.org>  wrote:
>>      
>>> Hi everyone,
>>>
>>> up for vote is to decide on a policy for RTC ("Review-Then-Commit") vs CTR
>>> ("Commit-Then-Review). Attached below are four options, ranging from the
>>> most conservative to the most liberal. Please vote on this, I urge everyone
>>> working with the source to vote within 72 hours. If you are only going to
>>> vote on one thing, vote on this one. :)
>>>
>>> Vote on the following alternatives
>>> -----------------------------------
>>>
>>> [ ] RTC for everything except trivial changes (e.g. comments).
>>>
>>> [ ] RTC for everything, except very small changes which are CTR.
>>>
>>> [ ] RTC for everything, except code which would take ~5 minutes to review.
>>> Such changes are CTR.
>>>
>>> [+1] CTR for trunk, RTC for all release branches.
>>>        
>> CTR for trunk, RTC for stable/release branches makes the most sense
>> for most server projects, and enables committers to easily do work in
>> trunk without burdensome process.
>>      
>    



Mime
View raw message