02.05.2013 Views

User Guide - Mks.com

User Guide - Mks.com

User Guide - Mks.com

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Freezing<br />

Members<br />

Controlling Members<br />

:member appears in the Revision field indicating the member revision<br />

will be demoted.<br />

3 Select a new state from the Demote to State list, for example,<br />

Development.<br />

4 To accept the new state, click OK (for multiple members, click OK to<br />

All).<br />

The member is demoted.<br />

When your development team has largely finished a portion of a project<br />

and some project members are in a stable state, you can freeze individual<br />

members within a project or sandbox.<br />

Freezing a member places it in a state that prevents changes from being<br />

made to the member information that resides in the project file. For<br />

example, you cannot update the member revision or change the attributes<br />

of a frozen member. Freezing is the opposite of thawing a member.<br />

Freezing restricts member information from being updated, preventing<br />

these members from being changed by accident. However, development<br />

work can still continue in the member file itself. For example, if new<br />

revisions are checked into the member’s archive, Source Integrity does not<br />

update the project’s member revision.<br />

Freezing is useful for facilitating:<br />

project checkpointing<br />

member promotion<br />

software distribution<br />

Freezing prevents changes to member information in the project, but does<br />

not affect the member file itself. Revisions can still be checked out,<br />

modified, and checked in, but none of the changes are included as part of<br />

the member information in the project.<br />

301

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!