[p4] Question about branching/integrating
chuck.karish at gmail.com
Mon Jun 14 06:27:42 PDT 2004
Branch from main at a point where you're sure that you'll take
everything. Integrate features from main to your new release branch
as they're finished.
A more radical approach: Make a permanent forward-development branch,
and integrate features from //depot/dev only when theu're ready to be
released. The main line stays clean, the developers grumble about
doing one more integration, the project managers love that release
readiness is predictable and that they control release contents.
On Mon, 14 Jun 2004 00:39:35 -0700 (PDT), David Rybolt <dagg at yahoo.com> wrote:
> I regularly run into this branching conundrum, and was
> wondering if anyone had any suggestions.
> My current directory structure looks something like
> this (only showing relevant directories):
> The 4.1.0 directory was branched from main about
> 3 weeks ago, and both main and 4.1.0 have had
> checkins since the branch.
> This was working great for a while. I'd merge
> the 4.1.0 code back into main as necessary, and
> everything was good. However, now my developers
> want to start checking in new code for a new
> release, but they don't know if it'll actually
> go to production before or after the code
> in my mainline.
> Any suggestions?
> Here is what I can't do:
> 1. Branch from main, because I might not want a
> lot of the recent main code.
> 2. I can't branch from the 4.1.0 branch, because
> merging it back into main would be a pain.
> Thanks for your help,
> Do you Yahoo!?
> Friends. Fun. Try the all-new Yahoo! Messenger.
> perforce-user mailing list - perforce-user at perforce.com
More information about the perforce-user