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

Re: Approach to a Website Staging/Production Environment

From: Tilmann Singer <tils_at_tils.net>
Date: 2006-02-14 20:16:32 CET

* Blair Zajac <blair@orcaware.com> [20060212 03:40]:
> I think you should actually use a production and staging branch. To
> help keep administrative burden down, use the svnmerge.py tool which
> is distributed with Subversion. This will automatically keep track
> of which revisions you've already merged over and which revisions are
> available to be merged. It's a great way of cherry-picking revisions.
> svnmerge.py keeps track of the already merged revisions in your
> branch by modifying the svnmerge-integrated property on the
> destination directory of the merge.

Thanks for the recommendation! It looks like with the svnmerge tool
the staging/production branches approach seems much more feasible.

> >The developers will have to use svn info to find out what version
> >their local checkout is at and edit the deploy_list files to tag their
> >changes as staging or production ready. I think that this will be less
> >tedious and less dangerous than dealing with branches. Experience will
> >show how it works out.
> This sounds much more tedious :)

Compared to svnmerge, yes ...

regards, Til

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Feb 14 20:18:22 2006

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.