Little Green Men ( [EMAIL PROTECTED] ) wrote:
> Hello,
> I have a little concept question.
> what should be the correct way of setting an cvs environment for several
> developers ?
[smc] How many is several? I will assume < 10.
> should we open a separate branch for each developer ?
[smc] No, not unless you have some specific requirement
that makes this a good thing to do. Ordinarrily, no need for that.
> and if so,
> what happens after i merge one branch to the trunk ? do i delete the
> branch
[smc] No, you pretty much _never_ delete branches. When you're
done with a branch, you just ignore it from that point on.
> and open a new branch
> for that developer ? or let him continues to work on that branch (which
> i guess will create problems on the second merge
[smc] If you were to go the route of creating separate branches for
each devveloper, then you'd probably want to make a new branch
whenever an old one was merged. But why the need to make branches?
Branches have there places, but this doesn't sound like one of them.
> because it will merge
> things that ware already in the trunk)
> and how do i keep truck of all the branches ?
[smc] Manually. Write it down.
> and final question, if i do decide to remove the branch after merge,
[smc] No, don't remove branches, you will only cause yourself
pain. Another thing when you create a branch, always use
a regular, non-branch tag to mark the origin of the branch,
otherwise,
you will have no way to refer to this point later, if you need to.
(i.e. later, when it is too late to do anything about it.)
example, to create a branch
cvs tag branch_one_origin everything
cvs rtag -b -r branch_one_origin branch_one everything
However, you haven't said anything that indicates you need
to use branches at all. why not just have everyone commit
to the same branch (or to the trunk?) Or is there some
specific reason this won't work for you?
Hope it helps
-- steve
[...]
