+1 here too. Most projects here fall somewhere in a spectrum between "do whatever you want in a branch" and "don't release without having others approve your work". Different projects put the point where CTR crosses over to RTC at different points.
*shrug* - Sam Ruby P.S. Personally a fan of CTR, but I'm starting to appreciate our infrastructure team's puppet workflow where everything (even one line changes) are done in a branch and everybody asks other person to merge the changes. https://cwiki.apache.org/confluence/display/INFRA/Git+workflow+for+infrastructure-puppet+repo On Fri, Nov 20, 2015 at 9:54 AM, Jim Jagielski <j...@jagunet.com> wrote: > ++1 >> On Nov 20, 2015, at 9:38 AM, Bertrand Delacretaz <bdelacre...@apache.org> >> wrote: >> >> On Fri, Nov 20, 2015 at 8:09 AM, Jim Jagielski <j...@jagunet.com> wrote: >>> ...httpd for example) uses RTC, CTR and Lazy Consensus >>> simultaneously and works like a dream.... >> >> Indeed - those are different tools that each have their own purpose. >> They just need to be applied in the right places and at the right >> time. >> >> -Bertrand >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
