[Wayne Smith]

Hi,

I wondering how everyone organizes their Subversion repository with regard to LabVIEW upgrades (e.g. 7.1, 8,2 8.6, 2009, etc). Is it better to create a new repository for each version of LabVIEW (so you don't accidentally recompile a previous version), or have one repository and create new folders for each version.

Example 1: A single repository

Quote

Main Repository

LV7.1

app1
app2
app3

LV8.6

app1
app2
app3

LV9.0

app1
app2
app3

Example 2: Multiple repositories for each LabVIEW version

Quote

LV7.1 Repository

app1
app2
app3

LV8.6 Repository

app1
app2
app3

LV9.0 Repository

app1
app2
app3

This is just a simplified representation, of coarse there are other organizational details such as branch/tag/trunk.

Thanks for the feed back

[Bab]

Hi,
well I use branches when upgrading Labview. First I make a new branch with the previous version of Labview (a copy of the Head revision of trunk), without switching to the new branch. Then I mass compile my working copy in the new labview version. I test it a little an try to build, then commit the changes onto the trunk.

My repository looks then like this:

Project1
---- tags
---- ---- [...]
---- branches
---- ---- LV7.1
---- ---- LV8.5
---- ---- [other branches...]
---- trunk

note: trunk now contains the LV9.0 Vis.

It works for me. I don't think I need anything fancier since I usually won't development or maintain the branches with old labview versions (they are actually more like tags...).
As for your examples, example 2 does not look so good in my opinion: you loose the history by using different repositories.

Any other suggestion anyone?

BaB