Getting test and production branches in SourceSafe

Greetings,

Well, I've searched everyone and compiled all of the information I can about how SourceSafe should be used to maintain a test branch and a production branch in the same database. I want to throw my compilation out there and see if you guys do the same thing. If you don't, why do you do it differently? Also, please point out where I am wrong. I'm restructuring some projects and I want to do it right the first time. (Note: I would LOVE to use SVN instead of SourceSafe, but alas, I am bound by the chains of the existing architecture.)

First, you add your code to a production branch ($/Production) to get it into SS. Then, you share that code into a test branch ($/Testing) to get copies of the files. Whenever you want to make a change to the file, then you branch the file in SourceSafe, check it out, and make your change. That file continues to be branched until you merge it back with the production version.

That's pretty much what I've got. Again, would you agree with that being the general procedure to get both branches in? Also, why would you use pinning? I understand that the point of pinning a file is to make sure that when anyone does a "Get Latest", they get that version of the file, but is there anything past that?

Thanks for putting up with my questions! I just enjoy getting the feedback of people who have been doing it much longer than I. One day, I will be there...

Kyjan

Getting test and production branches in SourceSafe - HOW?!