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

Re: Suggestions and pitfalls for a development/deployment setup.

From: Grant Rettke <grettke_at_acm.org>
Date: 2006-09-10 04:51:48 CEST

Quoting Walter Hop <subversion@walter.transip.nl>:

> Hi all,
>
> I am currently designing a SVN setup to use for our website and backend.
> This is the first time I am going to use SVN for a serious project, so
> I'd like to get it right the first time! I hope somebody with experience
> can give me some comments on the viability and possible pitfalls of a
> setup like this. I'll try to be as brief as possible!
>
> My goals:
> - Develop on a test server, and do controlled deployments to the
> production server.
> - Do periodic releases where all changes from the test server are merged
> into a production release.
> - Support for doing "hotfixes" on the production server and backporting
> them to the development machine; this should be as easy and painless as
> possible.

One option would be to set up a DEV, TEST, QA, and PROD machine.

Checkout your (development) trunk to DEV and do all of your work there.
Do all of your trunk testing on the TEST box.

Checkout your release branch to QA. *Export* your release branch to PROD.
Then, rsync PROD to QA. All of the changes you make on PROD would get captured
in your release branch.

This sounds way too easy...it probably isn't.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Sep 10 04:52:52 2006

This is an archived mail posted to the Subversion Users mailing list.