Re: Updating a live website with a post-commit hook script

On Thu, 2006-06-29 at 21:57 +0200, Ryan Schmidt wrote:

> Tags in Subversion are not like tags in CVS. In CVS, you "apply a tag
> to a file." A tag is a property of a file. (Or so I've heard. I never
> used CVS.)

It is, but the main reason you apply them is to group all the files
you want at once. That is, if you have updated your working copy at
some earlier time and your snapshot passes the testing, you can use
the rtag command to apply a specified tag to the repository copy of
all the files at the versions you have even if the repository now has
new untested updates. A subsequent checkout/update of that tag will
get exactly the same versions as the workspace where the tag was
applied.

> In Subversion, you copy the trunk (or the branch you're
> working on) to a directory called tags. And that's it. Usually you'd
> give each tag a new version number or date.

Then you'd have to keep track of the versions that are supposed to
be installed - and to back out you'd need the last known-to-work
version.

> But you could certainly
> have a tag called "ready for beta" and simply delete it and recreate
> it when you want to update it.

That sounds reasonable. Is there a way to rename existing tags? In
the CVS scheme I would use rtag to change the RELEASE tag to
RELEASE-1, etc. for a few downrev versions, then add a new RELEASE.

> Why is merging not an option?

The idea is to make the system foolproof so you can have different
groups coding, testing, and installing and the only way code gets
to production is by the testers marking it as ready in the repository.
Developers should never have to stop modifying the trunk and the
installers shouldn't have to keep track of anything to get the
latest known-working version.

Since subversion naturally groups files in a commit, maybe the
tagging operation isn't needed to identify a snapshot but you
still need a way to mark the points that have been tested.

-- 
  Les Mikesell
   lesmikesell@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org