Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m a bit new at using perforce and was wondering what I should/shouldn’t do…
I don’t have too much experience with the idea of branching out and I find myself looking through labels for past versions and bug fixes.
By the way my current setup is Perforce 2009.1 and visual studio 2008.
Thanks in advance!
The general branching strategy is to create a branch for mainline, a branch for dev and a branch for each release. Each branch allows for another line of development. The idea is that bugfixes will be made against the release branches, and then reverse integrated or “merged” into mainline / dev. Eventually, on a next release, dev will be integrated to mainline, etc.
The best thing to keep in mind with branches/integration is to always maintain a parent/child relationship with branches, going beyond that and integrating sibling branches can be computation expensive.
Does that help?