On Tue, Nov 27, 2012 at 2:12 PM, Armando Perico <peric...@usi.ch> wrote:
> This could be a good solution, however, the idea of having the files in
> different directories (moving for each status) is not really appreciated
> here :S
>
If you don't at least copy the final/release revs to tags, you are
pretty far away from normal svn workflow usage. And if you do, then
the concept of moving the working stages through branches makes more
sense. Note, however that from a user's working copy perspective the
items don't change their locations. You have a top-level directory in
the repository containing the file(s) you are tracking and check out
that directory. Then you use 'svn switch' or the tortoise equivalent
to move around among the trunk/branch/tag locations in the repository.
The result is that the workspace contains a copy of the work at the
specified stage but the relative locations of the checked out file(s)
look the same to you. IIf the workflow goes through different people
for different stages, then you might use the 'svn cp' to the next
branch/stage location as the handoff instead of anyone needing to do a
switch.
--
Les Mikesell
lesmikes...@gmail.com
