Re: replace a tag with a new version

Andrew Thompson wrote:
> For reference: I'm storing a copy of my website in Subversion. I'd
> like to be able to script an export of a "stable/current" release for
> rsync'ing to my web server. I can't say that trunk will always be
> usable.
>
> Should I just drop this line of thought and just be committing known
> good stuff against "current"?
>
> Would it be easier to just make trunk my stable/current version, and
> just have a branch version that I'm constantly merging back into
> trunk? (Seems like a lot of work.)

What I do with a current web project is to keep most general development
in /trunk, and maintain a /branches/stable branch to contain tested
(mostly) code that should be "live".

Occasionally I'll create a development branch for some more invasive
changes to the code that I'd like to apply to the trunk atomically (as a
merge), which I can then apply to the stable tree after making sure it
doesn't mangle any minor changes I've made in the trunk since creating
the branch.

I only create a tag for a "landmark" revision that I feel needs to stand
out in some way.

-kgd

-- 
Get your mouse off of there!  You don't know where that email has been!
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org