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

CVS and SVN: Tags and Branches.. A question of strategies

From: Peter Kahn <citizenkahn_at_gmail.com>
Date: 2007-03-02 16:04:11 CET

Can someone let me know what is a good way to approximate cvs tagging in svn
  if asking such a question means I'm trapped in a cvs mindset?

I'm trying to figure out how my team's processes will change as we move from
cvs to svn. I'm a long time svn administrator and long to move from cvs
back to a more modern SCM.

My requirement is to be able to build a copy of the last build + specific
changes only.
I'm building build.2 and it has 3 fixed bugs with associated revisions.
I need build.1 + those changes with no others included.

Our cvs process is:
- take the build_1 tag and clone it as build_2
- update the build_2 tag to include the bug fixed files at the right
- build from the build_2 tag

In svn, there are no tags only branches and revisions. So, it looks like
I'd need to:
- branch build_2 from the build_1 branch
- merge over the changes from a mainline to branch_2 (hoping that there will
be no conflicts.
- build from the build_2 branch

This seems complex to me. It feels like I'm bending subversion to
accommodate a practice that may have been valid for CVS, but makes no sense
in a SVN environment. does it seem like i'm trapped in a CVS mindset?

Well, I'd appreciate any feed back on this, because I'd really like to get
this right... Thanks.

Peter Kahn
citizenkahn@jabber80.com, pkahnpie1@AIM
http://kahnstipation.blogspot.com | http://analogoustendencies.blogspot.com/
Awareness - Intention - Action
Received on Fri Mar 2 16:04:40 2007

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.