Gerrit is being used by many large open source projects, It should be worth noting that those large open source projects have very, very different needs than a

Gerrit is being used by many large open source projects, It should be worth noting that those large open source projects have very, very different needs than a small development team working on a product together. The open source project likely isn't doing weekly releases (which require some sort of manual QA process, in the source article). A large open source project has hundreds of contributors, where reviewer time is scarcer than contributor time (and the pool of people to approve and commit a change is much smaller than the contributor pool). I think the OP's real problems are that: - an increased release frequency requires them to do more QA - their time spent in code review seems to be a function of how often they are "releasing", not how often people are making changes If the difficulty of making a release increases as you increase your release rate, you might be doing "agile" in a poor way.