On Wed, 17 Feb 2010, dcz wrote:
> Here is what I'm trying to do : some user (let's call them junior
> developer) should require their commit to be authorized by other
> (senior developer) before they would actually be committed.
You could require the junior developer to put a line like this
in the log message:
Approved by: <insert name of senior developer>
Then you could have a pre-commit hook that rejects commits from junior
developers, unless that line is present in the log message. If the
junior developer lies about whether the code has been approved, then
you have a non-technical problem to solve outside svn. You could also
extend this by requiring the log message to contain a reference number
to an external database that tracks code reviews and approvals.
--apb (Alan Barrett)
