RE: Merge in Revision Graph

Hauke writes,

> I'm currently evaluating migration of a project from IBM ClearCase to
> Subversion. There is one use-case that we often have, that is easily
> solved in ClearCase but I'm not sure what the right way would be in SVN:

If you are going to be the Subversion (including TortoiseSVN) specialist, or pioneer, for a project, it is a very, very good idea to read the Subversion book. That's available from http://svnbook.red-bean.com/ in various languages and formats.

> We often have this scenario:
>
> * Announce a release at a special point in time
>
> * Announce code freeze some time before it
>
> * At that point in time, create tag; i.e. svn copy the trunk to
> a tag dir
>
> * Release from the tag

Full answer: read and study chapter 4 of the book.
http://svnbook.red-bean.com/en/1.7/svn.branchmerge.html

Short version: this sounds like a case for a branch started at code freeze, and a release candidate tag from that branch. Then any bug fixes which have to be added can be added to the branch, subject to all the appropriate quality control and management you may need. Further release candidates can be made as new tags copied from that branch.

You can either delete discarded release candidate tags, which allows the same tag name to be used again, or keep them as RC1, RC2, and so on.

All this is Subversion in general, not specific to the TortoiseSVN client.

  - Mark.

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2932461

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-03-07 22:25:49 CET