News for hackers. Stuff that matters.
Re:Introducing code reviews to a team – Part 1 by sriram_iyengar on Friday November 18, 2016 @10:55AM (#12987582)
Good start and my best wishes. We follow these on stash using fork & pull request model, for a large project with 10 teams, each around 6-8 devs. - everyone has a fork - no one commits outside their fork - each module has 3-4 reviewers - good practices are constantly shared via sessions - wiki drafted and updated - comments are given reasoning with concepts, discussion threads and as well to other modules - object calisthenics, if required

There are no comments on this comment yet.