The Source Integrity Professional Edition User Guide - MKS

Getting Started With Projects, Sandboxes, and Members
Freezing Members
When your development team has largely finished some portion of a
project and some project members are in a stable state, you can freeze
individual members within a project. Freezing restricts member
information from being updated, preventing these members from
being changed by accident. For example, if new revisions are checked
into the member’s archive, Source Integrity does not update the
project’s member revision.
Freezing prevents Source Integrity from changing member
information in the member’s project file, but does not affect a
member file itself. Revisions can still be checked out, modified, and
checked in.
You can change the label or state of frozen members, but not their
attributes.
Freezing can be used immediately before a checkpoint operation to
ensure that no one changes the project or its members before the
checkpoint is complete.
When you open a frozen subproject member, you get the
checkpointed revision, if it is an archived subproject.
When you want to allow project members to be changed, you can
thaw them (see “Thawing Members” on page 107).
Source Integrity reports the availability of new revisions when
anyone checks them into the archive. Source Integrity does not
update the project to the latest revision, so an appropriate person
must make the decision to lift the freeze and update the project.
To freeze a member in the Windows interface:
In an active Project or Sandbox window, select the archived
member(s) you want to freeze and choose Member > Freeze, or
click (if added to the toolbar).
A snowflake symbol ( ) appears beside each selected archived
member in the window.
To make this command act recursively in all subprojects of the
specified member, make sure the Freeze Members option is selected in
the Recursion panel of the Personal Configuration dialog box.
106 Source Integrity Professional Edition