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

Re: Recommended svn work flow?

From: Gábor Szabó <szabgab_at_gmail.com>
Date: 2005-07-21 18:39:10 CEST

On 7/20/05, Scott Fenton <scott@tierra-innovation.com> wrote:
> - at some point, certain committed files (not all) are approved to move to
> the public web server. With cvs, these approved files are tagged 'LIVE' and
> then the tagged files are copied into a 'live' working directory (using cvs
> update -r LIVE) and then that 'live' directory is rsync'd with the public
> server.

In SVN you usually work in a directory called /trunk.

I think you could keep a copy of /trunk called /LIVE and then when you
would want to
move a file to the live server you would merge thoses specific files
from trunk to LIVE:

But this is not really how people usually work with Subversion.

Probably a better approach would be to keep all the files in /LIVE
then for every new
feature you would like to add create a branch in /branches/feature_x
Once you are ready with that feature you will merge it back to /LIVE

This is not exactly the same workflow but I think it will be cleaner
to work like this.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jul 21 18:41:22 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.