Releasing SW with Vault practices

[kasti]

I would like to ask you guys on how you go about releasing SW with Vault.

Our Vault DB layout looks as follows:

$/Project1
$/Project1/Source
$/Project1/Source/Imports
$/Project1/Source/Imports/Lib1exports
$/Project1/Source/Imports/Lib2exports

$/Lib1
$/Lib1/Source
$/Lib1/Lib1Exports

$/Lib2
$/Lib2/Source
$/Lib2/Lib2Exports

....


The libs are shared libraries with their own release cycle. They are pinned in the Imports Directory to a Label (nice feature btw).

In VSS we did the following when we got close to a release:

- Check out Project1 2 times to 2 different working folders.
One would be for the release (only minor changes, bugfixes etc) and the other where development was moving on
- Only the one for the release was allowed to be checked in during this stage until the release
- Once released, the "development" checkin could be done

This way, we did not have to create many branches in VSS which are a headache there.


In Vault, checking out 2 times for a developer is (I think) not possible. Since branching would be the better way anyway, I
tried this with the following problems with the imports directories:

- the directory shares are broken creating probably lots of extra Data in the DB
- labels get lost in the branch
- the imports\Lib directories are not pinned anymore (and can not be repinned because labels are not there). Repinning would not be an option anyway since we have about 50+ import libs.

Any suggestions on how to go about this ?

Thanks,
Herbert.

[lbauer]

You might get some ideas from these KB articles on using branches and labels, etc.

http://support.sourcegear.com/viewtopic.php?t=9

http://support.sourcegear.com/viewtopic.php?t=193