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

Re: Question about our branching deployment

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Tue, 06 Oct 2009 18:32:48 +0200

On 06.10.2009 12:30, Peter Heard wrote:
> 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 !

Please send your mail to the users mailing list. This has nothing to do
with the development of TSVN.


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-10-06 18:32:52 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.