I'm searching for resources about code review processes. Feel free to reply with your experiences too. I'm not interested in technical matters right now like how to automate parts of code review or your Opinion about the right size of a pull request. I'm asking about the social process of deciding when to merge. How do you ensure quality and keep development moving ahead without getting dragged down by disagreements? Boosts appreciated.
@clacke I tried this approach in one project, but we ended up in a situation "delivery" teams were developing mediocre code and a few folks from an infrastructure team were chasing new features by cleaning up and writing tests.
How do you make sure that XYZ improvement gets done?
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!