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

Re: Tags and branches handling

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: 2006-03-10 18:28:42 CET

Snurrre wrote:
> Hi Im a developer used to work in Clearcase.
>
> The questions below is asked because in clearcase I know how to handle these
> situation but im not sure how the best way is to handle it in Subversion.
>
> Q1: If tags folders is present in each project (many projects in same repo
> and each project has a tags folder) - how do I collect them all togheter
> (all with the same tag name, but located under different projects) so that I
> can release everything from different projects into the same release. (a
> very common workflow since the different projects are part of one release)

Create a separate 'project' for your releases. In there, you can create
another tag folder if you like, or just use the project folder itself.
Then, when you do a release, first create a new folder in there with the
name of the release. Then copy the corresponding tag of each project
into that folder.

The better way to go would be to reorganize your folder/project
structure so that every project gets its own repository. Then you can
create a tag in the 'main' project by using svn:externals.

> Q2: When working with many projects at the same time in your WC - Should you
> then manually create subfolders in your WC where you put your different
> projects and then you commit each project at a time? Or could you use
> svn:external or will you run into problem with commiting the external
> folders later?

If you use svn:external, then TSVN will show you a warning icon in the
commit dialog, if there are modifications inside the external dir and if
the external dir is from a different repository. If it's from the same
repository, a commit will also include the modifications inside the
external dir.

> Q3: How to close a branch after a merge - We will work with a branch only
> during the release cycle to support live version at the same time as main
> development is ongoing. - Is the best way to tag the branch? and if so since
> branches will exist inside different projects as for tags folder it seems to
> be a a lot of manual work here.

If you don't need the branch anymore, you can simply delete it.

> Q4: In Clearcase we used to tag/label only changed files and its directories
> for hotfixes and tag/label all files for full releases. In the first
> approach here something that you do with subversion?

You can tag single files with TSVN too. But I miss to get why you want
to do that. If you tag a whole directory, it doesn't use more space in
the repository than if you tag single files (copies are cheap, they're
basically only links).

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Fri Mar 10 18:29:02 2006

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.