On 27.07.2015 08:45, Dmitriy Setrakyan wrote: > On Sun, Jul 26, 2015 at 11:31 PM, Konstantin Boudnik <c...@apache.org> wrote: > >> I second. >> >> It's up to the community to go CTR or RTC but former has a way more >> flexibility and way speedier. Esp. considering that Ignite has great and >> functional CI in place. We are trying to get CTR running in Bigtop, but >> getting blocked by comprehensive CI being not ready yet. >> > The process in Ignite is that all committers work in separate branches. > Committers are free to commit into their branch as often as required. > However, the process that I prefer is that a review by another committer > must happen before a final merge to the master takes place. > > In my experience, I have seen the simplest of the commits break builds or > make wrong assumptions.
You do not fix this by implementing a heavyweight process. If merges to master regularly break builds, teach the person involved to run tests locally before merging (preferably after syncing their dev branch from master). A committer is supposed to be competent, after all. -- Brane
