[p4] Mainline vs. Promotion (Cascade) Branching model

Chuck Karish karish at well.com
Tue Dec 18 22:49:16 PST 2001


At 05:37 PM 12/18/2001 -0800, brad.holt at autodesk.com wrote:
>When the time comes for us to release, create our QA/Service pack branch, and merge our next version's already existing development branch back into the main, it is always a bit of a chore.  The temptation to just consider the new release's development branch to be the new main trunk is pretty strong.
>
>Please tell me why I shouldn't do this.  I'd bet there are reasons to do with future merging/common ancestors problems etc.

When a customer complains about a bug in a three-releases-ago product,
how do you bring the fix forward to the current release and all intervening ones?

Chuck Karish            karish at well.com           (415) 317-0182




More information about the perforce-user mailing list