[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Usage advice - personal branches

From: John <jsparrow_at_ecclescollege.ac.uk>
Date: 2005-07-09 17:44:58 CEST

I've been using SVN for about 12 months now, but I'd like some advice for
laying out busy, multi user repositories.

We have a policy of committing often (as savepoints, in case of source code
corruption - we use MS Visual Studio....!). This means that 70% or more of
revisions don't leave trunk in a 'good' state, and work is only partially
finished. Obviously this is a pain.

What I'm planning is to have a branch inside each project, for each
person working on the system. ie:


During normal work developers only commit to their branch (hence no problem
with 'savepoint' commits). When a feature is fully implemented it is merged
into trunk (and also trunk changes are merged into the personal branch).

Is this the best option? Or should I look at some form of distributed
version control system? In some ways I'd like my working copy to belong to
two seperate repo's: a personal, local one for regular savepoints, and a
central one for sharing.



To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Jul 9 17:47:14 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.