User Guide - MKS

Controlling Members
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 no one changes the project or its members before the checkpoint
is complete.
When you want to allow project members to be changed, you can thaw
them (see “Thawing Members” on page 272).
If a member is frozen, 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 thaw the member and update the project as a whole.
A sample freezing sequence is as follows:
Working with the Apex.pj project, a release engineer freezes project
member utility.dll at revision 1.2.
The snowflake symbol appears beside utility.dll, revision 1.2 in
the Apex.pj project window. (The snowflake symbol appears only in
the context of the project.)
A developer checks out utility.dll, revision 1.2, modifies it, and
checks it back in.
The new version of utility.dll is not accessible to the Apex.pj
project until revision 1.2 is thawed.
To freeze a member in the graphical user interface and Web interface
1 With a Project or Sandbox window open, select the member you want
to freeze.
2 In the GUI, select Member > Properties > Freeze.
In the Web, select Member > Freeze.
A snowflake symbol ( ) appears beside the selected member.
271