Release Mgt. w/Vault Cook Book?

[ppazderski]

I am investigating/evaluating Vault for use in our environment.
I have figured out the typical developer activities (Add, Check-in/out, Delete).
Here is a sample of my Add steps
- Review Vault Client Manual
- Place/create the new file in the correct subfolder of your Working folder
- In Repository, select the folder where you want to add the file
- Perform Add Files/Folders

Now my focus is defining cook-book steps for Release Mgt. activities so I can present them.
I stared reading the numerous articles, FAQ, help, messages, etc.
and I quickly became overwhelmed by all the info.
I am certain what I do now, someone has done before.
Since I do not need to reinvent, I hope someone will share these Release Mgt details with me. Specifically:
- For development builds, test loads, production releases, etc. when do you “label”, “pin”, “share”, “branch”, etc.?
- What steps do you take to assure security, integrity, repeatability, etc.?
- At which steps are there key options/decisions?
- Of what warnings do I need to be aware?

All assistance is greatly appreciated!
Thanks!
Regards,
Paul

[lbauer]

Here is a link to get you started:

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

Also review the chapter on Branches in Eric Sink's Source Control How To:

http://www.ericsink.com/scm/source_control.html

If other users have suggestion, please post here.