CODEWITHSUNDEEP
perforce
Miguel
Miguel

Reputation: 1177

Perforce best practices with Branching

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!

Upvotes: 0

Views: 7198

Answers (4)

randy-wandisco
randy-wandisco

Reputation: 3659

A Perforce consultant wrote a fairly short presentation called the Perforce Directory Standard, which gives pretty concrete examples of branching models to use for different styles of development and release maintenance.

https://www.perforce.com/blog/100607/perforce-directory-standard-pds

Upvotes: 1

Bryan Pendleton
Bryan Pendleton

Reputation: 16339

You'll find a number of helpful guidelines about getting the most out of Perforce here in the book Practical Perforce: http://shop.oreilly.com/product/9780596101855.do

Upvotes: 0

user100766
user100766

Reputation:

Besides what Blaskovicz said, I can also recommend the chapter on Codelines and Branching in the Perforce Manual.

Upvotes: 2

Blaskovicz
Blaskovicz

Reputation: 6160

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?

Upvotes: 7

Related Questions