Re: Branching Strategy

Eneko Gonzalez wrote:
> One more question: i've read that tags are branches are implemented the
> same way in svn. I've also read that is a good practice to branch when
> you are going to do a new release, so if you find a bug, you can fix it
> in its branch, and merge with trunk later. But if tags are branches are
> implemented the same way, do i need a new branch? Or can i make the
> fixes in the tagged release?

The differentiation between tags and branches is solely in the user's
eyes. Subversion doesn't care if you call it a tag, a branch, or a zebob.

Generally, tags shouldn't be updated, because you weaken the association
that a tag made today is the same tag you'll get if you need to
rebuild/fix/test something next week. You don't *need* to edit a tag.
Unless it was never deployed, you should branch from your tag, fix your
issue, and create a new tag. Now you have release 1.3.21b(or 1.3.22),
which you can look back into subversion and identify exactly what was
changed from the original 1.3.21.

-- 
Andrew Thompson
http://aktzero.com/
Interested in a hosted SVN repository? Email me, let's talk...
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org