My team is branching per release. Once code is moved to the testing
environment, it is branched. Bugs are fixed within the branch and the
branch is tagged with the official release. Bugs found in production are
again fixed in the branch and a new tag is created for the re-release.
My question is: With this method, a lot of branches and tags are
created; is there a way to allow users to decide whether or not they are
downloaded to the local machine or archive them so they aren't
implicitly retrieved? Obviously, they can be deleted from a user's
machine; but if the user decides to update the root, the directories
will come back. This could eat up user resources pretty fast. Does
anyone know of a way around this problem?
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Aug 26 22:47:39 2005