Hi again!
I have noticed that most of the merging examples in
the svn1.1 book seem to share the following trait: in
the case of multiple developers, 1 developer is on a
branch, and 1 developer is on the trunk. Is this a
typical, accepted (recommended?) usage with svn?
Arguing for a finer clarification, does the trunk in
these examples actually serve the purpose of an
"integration" branch? That is, if there are 4
developers on a project, is it expected that 3
developers will all work on their own branches, with
one lucky developer working on the trunk, with the
other developers eventually merging into the trunk
when they are ready?
Past experience with other tools/groups has had me in
situations where ALL developers were on developer
branches, and each developer eventually merged to an
integration branch, which was eventually merged to a
"main" when work was complete. The latest (i.e.
"good", "working") version was always located on main.
Integration activities only broke the integration
branch.
Are there issues/limitations that I should be wary of
if implementing such a branch/merge-intensive process
with svn where all developers work on a branch, and
all merge to an integration branch?
Thanks,
D.
__________________________________
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.
http://promotions.yahoo.com/new_mail
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Oct 7 21:43:52 2004