Chris.Fouts@qimonda.com schrieb:
> [...]
> I like the idea of developers having their own branches, so they
> can commit their work without affecting others.
>
> A compromise to having private branches and developers committing to
> trunk is to have an integration branch off the trunk, which developers
> can do their work on.
>
> To the OP, I don't see an issue to how you're using SVN; that's exactly
> how we're using it; of course we only have 4 developers in my group) so
> we're able to manage it.
>
The issue I'm seeing is that this will create isolated branches that
will have to be merged into the main branch at one point, which will
lead to conflict situations which can be quite huge meaning many changes
over a long period of time. If the changes the developers are doing are
on isolated parts of the system using the main trunk to do the work will
lead to smaller conflicts which can be resolved on a per commit basis
quite easily if nessecary. If of course the changes you are doing are
all interrelated and most developers work on the same files then it is
better to use a branch. I also see a tendency to communicate more over
the code if everyone works on the same codebranch instead of having
their own private playground but this is purly my opinion.
Regards
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu May 10 15:58:24 2007