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

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

From: Peter Kahn <citizenkahn_at_gmail.com>
Date: 2007-03-05 14:42:35 CET

Thanks for the info. My basic question is
    "what's the best way to replicate the following CVS promotion based
development pattern in SVN":
            - all developers work on mainline
            - when we have a new build, we duplicate an existing tag and
update it with new versions of files on the mainline.
            - the new tag contains some, but not all updates since the last

     [for those unfamiliar with cvs, a tag can be viewed as a group of files
each at a specific version]

So, I'd like to have a flexible structure that allows me to group a variety
of different versions of files together and call them a build. In CVS, I
can use a tag (or a branch as well) for this. In SVN, I believe that my
only option is to branch & merge (agreed, with the tags branches being read
only after creation).

Finally, its possible that SVN isn't an option for us because the benefit of
tags is so great that another SCM (like p4 perhaps) is a better fit for our
environment. If that is the case, then we'll look elsewhere, I just want
to make sure that I'm not missing something here...

{it is also possible that our current promotion model isn't ideal either and
was developed only because of how CVS handles branching}

Thanks again.

On 3/3/07, Karl Heinz Marbaise < khmarbaise@gmx.de> wrote:
> Hi Peter,
> > My requirement is to be able to build a copy of the last build +
> > specific changes only.
> > example:
> > 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
> > versions
> > - build from the build_2 tag
> If i understand this process well it seemed to me that you've used
> branches instead of tags,... may be you can give a little more details
> e.g. how you did this in CVS (i appreciate to learn things)....
> >
> > In svn, there are no tags only branches and revisions.
> This statement is from the technical point of view correct, but if you
> take the view that you define a tag as an read-only area then you are at
> the point of CVS, cause in CVS you have to make a decision between tag
> (cvs tag) and branching (cvs tag -b).
> The way you decide between tags and branches in SVN is currently only an
> agreement, which means you put a tag into the "project/tags" directory
> and a branch into the "project/branches" directory.
> Kind regards
> Karl Heinz Marbaise
> --
> SoftwareEntwicklung Beratung Schulung http://www.soebes.de
> Dipl.Ing.(FH) Karl Heinz Marbaise email: info@soebes.de
> Tel.: +49 (0) 2405 / 415 893 ICQ#: 135949029
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org

Peter Kahn
citizenkahn@jabber80.com, pkahnpie1@AIM
http://kahnstipation.blogspot.com | http://analogoustendencies.blogspot.com/
Awareness - Intention - Action
Received on Mon Mar 5 14:43:05 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.