Hot take: in-house development has been influenced too much by the GitHub open source PR driven development process. A process driven by zero trust doesn’t fit well in a team with trust.
88
596
1,709
Conversation
Replying to
GitHub adds too much friction. Gerrit workflow is really a lot nicer. Also, need automation set up for a bigger project.
It works well to require a set number of reviews (usually 1, sometimes 2) and have powerful CI infrastructure quickly getting it tested + merged.
Replying to
I think it depends on the kind of project.
If something goes into production quickly based on what gets merged, that's different than having a release cycle where there's time to stabilize things before an actual release.
1
4
Show replies
The GitHub workflow copied by everyone (GitLab, etc.) is horrible.
You have your local repository but also your own unwanted remote repository to manage too, or branches in the main repository to manage yourself if you have access, which is still an annoyance. Becomes a mess.
3
I can second a positive review for gerrit. We are using it in VPP and it’s excellent and very flexible. And with change-id one can do some extremely nifty stuff, like track “same” changes across branches, etc.
1
2