I'm currently using CVS to track the development of some websites,
between a 3 man team consisting of myself, as a developer, and 2
designers, who aren't particularly technical.
I'd like to move to using SVN, but I'm not sure how to track the live
version (the one that gets displayed on the public website, we have
updates of the latest stable code every 15 minutes from a cron job) - at
the moment we just move a LIVE tag to the latest stable version of
files.
>From what I can see, using SVN would involve maintaining a full branch
of the site for the live version, which is likely to confuse the
developers (it slightly confuses me, since I've never really used them
:P), who can just about understand the concept of tagging once shown.
The thought of teaching them to do merges to a different branch is kinda
scary, although I'm not really sure what it technically involves - I'm
currently setting up a repository to play with and try to work things
out, but wanted to know if anyone is in a similar situation, and has
some advice?
I'm not averse to writing some scripts to check for the latest versions
if that's what it takes, but I'd like to keep the process of marking a
file as the stable version as simple as possible, so that we can get on
with doing our jobs, instead of playing with the VCS.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Feb 21 06:55:54 2004