Using gerrit (or similar tool) on a team where multiple devs work on a single feature

Posted by Bacon on Programmers See other posts from Programmers or by Bacon
Published on 2013-05-13T21:41:53Z Indexed on 2013/10/17 22:19 UTC
Read the original article Hit count: 227

Filed under:
|
|

We have a team of roughly ~8 devs who regularly work on the same feature over the course of a 3 week sprint. It isn't quite pair programming, but in our current workflow devs regularly push up incomplete code for a colleague to complete. This worked fine before we introduced Gerrit, but now our commits need to represent chunks of test-passing, complete, logical functionality, and so the model breaks.

My only idea is to have everybody push up to a separate, untracked branch up until the functionality is ready for review, then squash everything into commits that make sense and push up. Is there another Gerrit-ized workflow that could work?

I know this is a widely discussed topic on Google Groups, and that there has recently been some discussion of Gerrit topic reviews, but I wanted to see if there is anybody out there using Gerrit in this way, and what the suggested workflow would be.

© Programmers or respective owner

Related posts about version-control

Related posts about git