Re: CVS tools to allow for code review / merge management

[Paul Sander]

You might consider a simpler change management system that doesn't
involve the second repository.  If you search through the info-cvs
archives for submit/assemble or release/integrate, you'll find a
very detailed description of a method that tracks manifests and
changelists.  It's much lighter weight than the system you describe,
and it provides the tight integration with the defect tracking system
and throw-back capability that you require.

The key to the process is that the code that's eligible for the
build lags behind the latest committed revisions.  The formalized
hand-off points carry the proper code forward in the process while
allowing developers to commit without restraint.

--- Forwarded mail from address@hidden

I'm looking to either use or write a tool that would allow us to achieve 
the following workflow with our CVS repository:

- Developers write code and commit changes
- Lead developer reviews the code changes, and either signs off on it or 
sends it back to the developer with comments
- When lead developer signs off on it, code is moved/merged into a 
'clean' repository from which clean builds/dists can be produced, 
testing suites run against, etc...

--- End of forwarded message from address@hidden