[Kolab-devel] Code revision for kolab

[Christoph Wickert]

Hallo world,

recently some changes have gone into the repo that confused some contributors. 
Therefor it was suggested to introduce code reviews before committing changes.

The question is: Do we need to go that way? And if so, is there a nice 
workflow that will not slow down development too much? I think of a tool like 
'gerrit' [1] but I wonder if something similar is available for mercurial.

Regards,
Christoph

[1] http://code.google.com/p/gerrit/

-- 
Christoph Wickert
Senior Engineer

Kolab Systems AG
Zürich, Switzerland

e: wickert at kolabsys.com
t: +49 251 871 369 77
w: http://kolabsys.com

pgp: 85DACC63 Christoph Wickert
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.kolab.org/pipermail/devel/attachments/20101012/697e7168/attachment.sig>