Gavin 'Beau' Baumanis wrote:
> @Ryan, I assume that your point is that I would still perform the Merge
> operation - but into a TAG as opposed to a branch.
No, you don't need to merge at all (unless what you have on trunk isn't
completely consistent). Normally, you do all of your development on trunk and
when that is ready to go into production (ALL OF IT, not just some files), then
you create a tag based on the tip of trunk (otherwise known as HEAD). These
tags are then read-only (by convention, though you can enforce that by a
pre-commit hook).
> And instead of relying on "revisions" - I would have the naming of the
> tag to assist with "rolling back" changes made (in error) to the
> production system.
No, you 'switch' to a tag to put your current best release into production.
Then when you are ready to move then next release into production, you switch to
the next tag. Reverting to a previous state is as simple as switching back to
the prior tag. No merging is involved in this scheme at all.
John
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-03-07 13:22:39 CET