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

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

From: James Tikalsky <TIKALSKY_at_michaels.com>
Date: 2007-03-05 16:36:42 CET


From: Peter Kahn [mailto:citizenkahn@gmail.com]
Sent: Monday, March 05, 2007 7:43 AM
To: info@soebes.de
Cc: users@subversion.tigris.org
Subject: Re: CVS and SVN: Tags and Branches.. A question of strategies

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 build.

Forgive me if this is obvious, but I'm confused. You say that you copy
an existing tag and then update it with new versions of files from the
trunk/mainline? How then to you commit your revisions to the repository?
CVS tags are "sticky" (meaning that you can't change tagged files and
check in a revision) aren't they?

ASCII Art Diagram:

[Working Copy of Trunk] ------------|----------------------------->
[ongoing develoment]
                                   Tag1 .
                                            Copy of
                                         Trunk Changes
                                           After Tag1
[Working copy of Tag1] -------------| {Mix of Tag1 and trunk}

James Tikalsky
Fort Worth, TX

Scanned by IBM Email Security Management Services powered by MessageLabs. For more information please visit http://www.ers.ibm.com

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Mar 5 16:37:53 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.