Hi Mark. [moving to dev@ - there's nothing secretive about this...]
It's a valid question and we aren't a CTR project yet. The discussion you're referring to [1] is on hold as Jay has proposed to document the workflow first and then do the vote on it. Also, I believe, the implementation would be contingent to the availability of new CI. The sentence you're referring to doesn't allude anything about CTR vs RTC flows. It seemly states that a committer has commit-bit to put patches into VCS. It doesn't say anything in the effect of "no need to wait for a project committer to review the patch..." The email content is pretty much a copy from the standard ASF template [2] Hope it helps to clarify the situation. Best, Cos [1] http://is.gd/C2avEy [2] https://community.apache.org/newcommitter.html On Fri, Jan 23, 2015 at 10:37AM, Mark Grover wrote: > Hi Bigtop'ers, > That's awesome that we have new committers. > > I noticed that our new committer emails mentioned: > > > *Being a committer enables easier contribution to the project since there > is noneed to wait for a project committer to put the patch into the version > controlsystem. This should enable better productivity and turn-around.* > > I think we had a talk about making the project Commit-then-review but > decided against it for now. It's possible I missed it but I can't find any > reference to us being a CTR project in the email. I didn't want the new > committers to feel I was picking on them or something so decide to decided > to send it to private@ instead of dev@. Hope that's okay. > > Thanks! > Mark
