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

general subversion theory for developers?

From: Sean Moss-Pultz <sean_at_moss-pultz.com>
Date: 2004-01-07 11:33:51 CET

I have all the software team at my new job using subversion. We all
agree that it's a fabulous program. I'm sort of the de facto admin so I
was hoping users could give me some suggestions on the their favorite
ways to code in a team environment. For example right now there's about
6 of us all committing to the trunk. I'm only using branches to mark
releases of our code. This seems to work very well because we are are
(guaranteed to be) working on the most recent version and merging is
kept to a minimal. We are going to expand to about 20+ developers so
I'm concerned that the "all commit to trunk" method is going to run
into some problems. I've read some CVS admin theory but it seems to
destroy the "community" programming that subversion introduces (while
all committing to trunk). They say to give everyone their own
"sandbox", by making a branch for each user, and then one admin merges
all the changes back to the trunk, creates all new branches (or they
can update theirs) and the process continues forever in this manner. Do
any of you guys use a method that you feel works particularly well? I
would love some guidance.

Thanks in advance!


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jan 7 11:35:01 2004

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.