code reviewing and test enforcement?

We're trying to use subversion instead of aegis for recent projects. For
no particular reason, really, just to try out new stuffs. Also,
subversion has tools like TortoiseSVN which makes it convenient to use.

Using subversion, for projects involving several developers and a code
reviewer, how might one implement obligatory testing (i.e., a test
script has to be run first and succeeds before commit can continue) and
code reviewing (i.e., when a developer commit a change, it goes to the
code reviewer first; if the reviewer rejects the code, nothing is
committed). Developers use "svn diff" + email the reviewer instead of
"svn commit"? Use two repositories?

-- 
dave
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org