We are using Subversion to manage website development (actually e-learning, but it comes down to more or less the same thing).
Are current process is the following:
- All developers/designers etc check out and work on their own working copy, in the normal way
- Once we want to make a release to QA, we make a tag for the release, usually called YYY_MM_DD_n
- Then, we do an export, and ZIP it up. We do this rather than a check out so there are no .svn folders in the releases, and so that people are not tempted to/do not accidentally make changes directly on the release.
- Finally, we FTP the ZIP files to the QA server and unzip to test (or we upload the ZIP file into a learning management system depending on exactly what we're doing).
- When we do a production release, we follow the same steps, usually sending the ZIP to the client.
I hope this is helpful.
From: Brendan van Drempt [mailto:Brendan_vanDrempt@scholastic.com.au]
Sent: Thu 27/05/2004 01:27
Subject: Subversion and Project Environments (Dev / Test / Prod)
I am in the processing of setting up Subversion to manage the development of
Subversion Repository on Windows Server machine running SVNserve. Windows
development machines running TortoiseSVN client. (soon to add mac
development machines, when we decide on a suitable mac subversion client)
* What is the best way to implement Subversion across my Dev / Test /
* Should each environment be a 'working copy' of the repository, and then
use a client tool to update to particular revisions? (in addition to the
working copies of the developers)
* Should I be using 'tags' to set releases?
Need a bit of clarity here.
Brendan van Drempt
Analyst / Programmer
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Thu May 27 02:42:37 2004