Derek Price wrote:
I believe integrating this exactly as you specified would slow your
developers down considerably.
My experience tells me the exact opposite. By ensuring a sound
repository and force sharing of knowledge through reviews, the
*team* as a whole will benefit considerably.
If you are trying to integrate a large number of unknown developers, as
often happens on open source projects, ...
My experience tells me that reviewing code gets important when
the team exceeds two developers. People have different background,
different habits and different knowledge. Actually most programmers
like to be reviewed; It feels safe having someone else verifying
their design and logic. It takes a little bit of extra effort, but
that is gained by the shared knowledge you get back for free.
But of course, projects differ; I can only speek for what I am used
to (but having been there a while, that is a lot). And of course if
a feature like this ever find its way into CVS it should be optional
by all means.
_______________________________________________
Info-cvs mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/info-cvs
