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

Re: Branch suggestions when working with multiple offices

From: Ryan Schmidt <subversion-2007b_at_ryandesign.com>
Date: 2007-10-21 23:14:51 CEST

On Oct 21, 2007, at 13:10, Steve Finkelstein wrote:

> I apologize if this question is too generic for this particular list.
> I'm looking to draw up a strategy for branching our subversion
> repository in an intuitive fashion. Something that will ultimately
> make lives easier for our inhouse developers and outsourced developers
> which are located overseas.
>
> Would anyone be kind enough to point me to some literature as to some
> different approaches which can be taken? I'd like to branch off and
> have folks stop committing all code to trunk at my earliest
> convenience, which will be when I'm educated on the proper approach.

Have you already read the book? For example this section discusses
merging, and thus touches on some reasons why people branch.

http://svnbook.red-bean.com/en/1.4/svn.branchmerge.commonuses.html

But there's nothing necessarily wrong with having everyone commit to
the trunk most of the time.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Oct 21 23:17:39 2007

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.