I have few questions regarding Vault usage.
I have 2 repositories. One holds development version of code and other repository holds staging server code. My staging server code is always clean code and my development server code (Many of the files) will be checked out by my developers.
1. If I label my Development code at certain stage (Say Version 1.0). After my developers modified many files. Now I want to checkout version 1.0 file for my build. How will I check out these files (Lebel version 1.0, not latest version)? Is it possible to check out label version at root level or do I need to check out project wise?
2. If I want to move Version 1.0 from Development repository to Staging repository (right now My staging repository holds Version 0.9) what is the best way to export files? I need all developers comments also.
3. If I want to move files from Staging to Development repository including comments ( worst case) how will I move with a single click (I mean not individual files/ Projects, all projects at a time)
Please let me know and advanced thanks for your help!
Vault Repository Import
Moderator: SourceGear
Vault doesn't yet have the ability to move files (and their history) across repositories yet. We plan that for the next major version. You would have to do a Get on one repository and an Add or Checkin on the 2nd repository to move files.
If you want to retain history, it would probably work better to use the Branch command within a single repository. Branch will retain the history of files at the time of the branch, but from that point forward, changes to each branch will be part of its own history.
Note that Label allows you to set a snapshot on a version of a tree, but it doesn't work so well if you want to start editing at a previous version. So, you can label a tree as 1.0, and do a Get on that label to retrieve the files to a working folder or a non-working folder. But, if you want to make changes that apply to only 1.0 and not the rest of the tree, it doesn't work so well.
In that case, Branch also works - Branch the tree to a 1.0 branch, which allows you to make edits to 1.0 while your main development continues. If you want to move changes from 1.0 back into the main tree (or vice versa), you can use the Merge Branches command.
I hope some of this makes sense
If you want to retain history, it would probably work better to use the Branch command within a single repository. Branch will retain the history of files at the time of the branch, but from that point forward, changes to each branch will be part of its own history.
Note that Label allows you to set a snapshot on a version of a tree, but it doesn't work so well if you want to start editing at a previous version. So, you can label a tree as 1.0, and do a Get on that label to retrieve the files to a working folder or a non-working folder. But, if you want to make changes that apply to only 1.0 and not the rest of the tree, it doesn't work so well.
In that case, Branch also works - Branch the tree to a 1.0 branch, which allows you to make edits to 1.0 while your main development continues. If you want to move changes from 1.0 back into the main tree (or vice versa), you can use the Merge Branches command.
I hope some of this makes sense