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

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