User Guide - MKS

Viewing and Editing
Member Histories and
Revisions
9
KEY TERMS: member history, archive information, revision information, working file,
locking, unlocking, branching, merging
While sandboxes and projects allow you to manage and access project
members and the contents of individual members—the history of changes
are saved in member histories.
Source Integrity lets you save and recreate every stage (or revision) in the
development of each member you use.
When you make changes to a project member and check it back in, your
changes are automatically added to the member history. If you ever need
to see that version of the member again, check out the appropriate revision,
and Source Integrity rebuilds an exact copy for you.
This chapter provides details on the following:
“Viewing a Member History” on page 280
“Viewing and Editing Archive Information” on page 282, and
“Viewing and Editing Revision Information” on page 284
“Viewing an Annotated Revision” on page 286
“Viewing and Editing Revision Labels” on page 288
“Viewing a Member’s Working File or Revision” on page 291
“Promoting Revisions” on page 292, and “Demoting Revisions” on
page 293
“Locking Revisions” on page 294, “Unlocking Revisions” on
page 295, “Locking Multiple Revisions” on page 296, and “Managing
Revision Locks” on page 298
“Setting the Member Revision” on page 300, “Deleting Revisions” on
page 301, and “Comparing Revisions” on page 301
279