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

Question about our branching deployment

From: Peter Heard <peter_heard01_at_hotmail.com>
Date: Tue, 6 Oct 2009 03:30:51 -0700 (PDT)

Hi, I wonder if anyone could help. We are looking at implementing a seperate
branch of our software using tortoise svn. This custom software will have
some unique features that we are creating the branch for. However we would
like to be able to port changes across from our main trunk to the branch.

What I want to know is what (in peoples opinion) is the best way of keeping
the core parts of the project inline with each other?

Do we implement a system where we should force all devs and bugs to have a
number assigned to them and then have a code file list attached to them that
we migrate across to the branch? Are there any loose guidelines that will
help us decide what we can branch across?

Its an asp.net project with 2 web sites and 1 class library.

Any rough guidelines would be much appreciated as Ive never done this before
and I have to work out how to do it Confused !


View this message in context: http://www.nabble.com/Question-about-our-branching-deployment-tp25766329p25766329.html
Sent from the tortoisesvn - dev mailing list archive at Nabble.com.
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-10-06 12:31:23 CEST

This is an archived mail posted to the TortoiseSVN Dev mailing list.

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