________________________________
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