fabien wrote: > ... For the new policies, we are setting a code review process: every commit > has to be validated by someone else before being merged.
Good luck with that! Some engineers take to it very well, others complain that it just slows them down and provides no benefit. But code reviews are good for the code, the coder, the reviewer and the whole engineering team if done well. fabien wrote: > It's complex, because it requires more people in the quality team. (or slow > down the merging process.) Yes, I used to manage that! Code reviews done by other engineers means that the quality team doesn't have that extra load, though. ------------------------ Regards, Geoff Seath Solutions Ltd (http://www.seathsolutions.com) -------------------- m2f -------------------- -- http://www.openobject.com/forum/viewtopic.php?p=42319#42319 -------------------- m2f -------------------- _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman2/listinfo/tinyerp-users
