Beta vs. Production

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
Noble Bell
Posts: 15
Joined: Fri Nov 07, 2008 9:58 pm

Beta vs. Production

Post by Noble Bell » Mon Jan 05, 2009 2:16 pm

This may not be the best forum for this post but I did not know anywhere else to ask it.

What is the best way to handle having a project for beta and a project for production? Should I keep just the beta in source control and copy the project to a new production folder when ready to deploy or should I have both folders under source control? Is there an easier way to do this?

Thanks in advance,
Noble

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Re: Beta vs. Production

Post by lbauer » Tue Jan 06, 2009 7:50 am

This is a common question. One way to manage development and releases is to use branches. Here are some links to help:

http://www.ericsink.com/scm/scm_branches.html
and
http://support.sourcegear.com/viewtopic.php?t=193

Once you have branched, you can use the Vault Merge Branches Wizard that allows you to merge changes from branch back into trunk, or trunk into branch.
Linda Bauer
SourceGear
Technical Support Manager

Post Reply