[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: Bob Proulx <bob_at_proulx.com>
Date: 2005-04-25 02:30:37 CEST

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?

Much of those "best practices" came from using CVS or RCS before it or
other revision control systems. In RCS/CVS it was considered good
practice to make a branch when making a release so that it would be
ready to go in the event that you needed it. By making the branch and
releasing from it you were ensured that you were set for future

In subversion the tagging and branching methodology is significantly
different. It is much easier to make a branch. So it might not be as
important today to branch as part of the release. As long as you have
tagged it properly you can always branch later if needed. There is
more flexibility. So now it is really more your choice.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Apr 25 02:32:28 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.