Ok. However, I don't see how Subversion, or anything else in the mix, can
manage access control to the repo such that a user/developer can update the
feature branch but not update the rest of the repo. Does such a capability
exist in Subversion or something related?
-Matt
At 2/8/2006 10:45 AM, Ryan Schmidt wrote:
>Sounds like you want a "feature branch." When a new suggestion comes
>in, you can copy your current development code (probably the trunk)
>into a branch, make the changes there (by applying a patch provided
>by the user, for example, or you could even give that specific user
>access to that specific branch), and see how they do. If you hate
>them, you delete the branch and forget about it. If you love them,
>you merge the changes back into the trunk.
>
>http://svnbook.red-bean.com/en/1.1/ch04s04.html#svn-ch-4-sect-4.4.2
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Feb 8 17:56:34 2006