> Does SVN support the ability to apply policies over
> directories? For example, can I limit access to specific
> directories under the tree to different groups with different
> levels reading and writing capabilities? Can I take it one
> step further and lock down the tree and prevent commits to
> it, like in the situation where we have a release candidate
> and we don't want anyone making unapproved check-ins?
Others have answered on per-directory access control, but re: releases,
seeing as every commit to a SVN repository is effectively a "branch"
because its revision history is for the whole repository and not per
file, you can build a release from any revision you like without any
need to stop ongoing develop on the Trunk.
Branching is no big deal in SVN, it is effectively making a
copy/shortcut to a revision in history - the info you need is all in the
subversion book under branching and tagging.
It'll probably be useful for you to read this section
http://svnbook.red-bean.com/en/1.1/ch04s04.html#svn-ch-4-sect-4.4.1
which describes the "best" practice usage of SVN - i.e. develop new
features in Trunk, release to a branch and test, and then tag and
release the "tagged" code.
The tag is an unchanging snapshot in time, the branch will start off
that way, but may be updated for interim fixes/releases to released
code, and new work continues in trunk.
Regards,
Mark
==============================================================================
Please access the attached hyperlink for an important electronic communications disclaimer:
http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html
==============================================================================
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-07-08 14:26:16 CEST