Using activities for branching

Hi,

I have trouble understanding how activities can be used effectively
for branching purposes. When one makes branches in a version history
this usually leads to a tree with different lines of descent.

As far as I see it is not possible to have work going on in different
branches at the same time, because in a version history there can only
be one checked-out version, which stems from the fact that a VCR has
at most one checked-out version. In other words, the branches are not
independent. That is not what I am used to with version systems.

Workspaces are of no help here, because you would have to introduce
a new VCR with an independent version history. There is no permanent
link between that version history and the one the workspace was created
from. With workspaces one can't "grow" branches on an existing version
history. Once a workspace is gone its version history is gone as
well.

Clearly, it should be possible to work in parallel and maintain the
history of all this parallel work. With workspaces you have parallel
work without a parallel history, whereas with activities you can have
a parallel history, but which can't be created in parallel.

Regards,

Werner.
-- 
Werner Donné  --  Re
Engelbeekstraat 8
B-3300 Tienen
tel: (+32) 486 425803	e-mail: werner.donne@re.be

Received on Friday, 24 March 2006 17:48:14 UTC