[p4] User initiated Codeline Freezes

Chuck Karish chuck.karish at gmail.com
Sun Aug 26 18:02:45 PDT 2007


On 8/26/07, Roy Smith <smith_roy at emc.com> wrote:
> On Aug 26, 2007, at 5:34 PM, Chuck Karish wrote:
>
> > For one of the teams I support the compromise to this is to start
> > an advisory
> > code freeze on the main line at the pre-announced deadline, and
> > open the
> > main line back up after the continuous build-and-test system
> > produces clean
> > results that include the last changelist submitted before the
> > deadline.
> >
> > As soon as we see the clean results we announce that the freeze is
> > lifted
> > and we down-integrate to the release branch from the changelist at
> > which
> > the clean build and test were done.
>
> What is the advantage of doing this compared to just branching at the
> deadline?

We start with a credible release candidate without having to use cherry-
picked changes to fix it from the very beginning.  A working snapshot
of the code base is a deliverable that Development owes to Release
Engineering.

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



More information about the perforce-user mailing list