[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Branching Strategy

From: Hakan Koseoglu <hakan.koseoglu_at_gmail.com>
Date: 2005-04-25 09:33:41 CEST

> 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?
They are the same thing. Only difference is in practice, what you do
with the copy of the trunk you just released. You can always treat it
as a branch or you can (in your mind) distinguish between tags and
branches as two separate things, with different practices (tags are
R/O, branches are R/W). As long as it is clear what you can do in a
particular subfolder (all branches and tags are essentially subfolders
(copies of trunk), you are safe.

It is somewhat confusing after CVS and other rcses where tags/labels
are not the same as branches. Some people might consider a weakness of
Subversion, I count it as a strengt. Your mileage may vary.

Hakan (m1fcj)
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Apr 25 09:35:36 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.