Re: Web development

Jon Wood <jon@jellybob.co.uk> writes:
> 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 issue is probably that tagging is a total pain in the neck in
CVS. In subversion it is much easier. I'd suggest that you just
maintain a "release" or "live" branch and do it exactly that way. They
probably will find subversion's branches much easier to use.

> 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

In most cases, it should involve just one simple command --
svn merge.

-- 
Perry E. Metzger		perry@piermont.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org