Process control for Subversion?

I am getting started using SVN for a new project. I'm fairly familiar with
the basics of its operation and administration. My question is this: Are
there any formal process control mechanisms that can work with SVN?

For instance, I would like to know how to do the following tasks:

* Given a change request, initiate work on a codeline for that change
request.
* When finished with changes to a codeline for a given change request,
submit the code changes for review to another developer.
* When finished with changes to a codeline for a given change request,
submit the build products for execution review to another developer
* Work on multiple independent pieces of work so that they are insulated
from each other. For instance, I might work on the same file Foo.cpp in two
different work 'areas' simultaneously.

Are there recommended best practices for doing this? Are there any
open-sources tools to help automate the procedures for addressing the above
scenarios?

Thanks,
--Steve (mrstevegross_at_gmail.com)

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1051036

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-01-27 21:17:21 CET