02.05.2013 Views

The Source Integrity Professional Edition User Guide - MKS

The Source Integrity Professional Edition User Guide - MKS

The Source Integrity Professional Edition User Guide - MKS

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.

Checking In a Member<br />

Starting a<br />

Branch When<br />

Checking In a<br />

Member<br />

Checking In a Member<br />

2. When finished, click OK to accept changes, or Cancel to close the<br />

dialog box without changing any settings.<br />

To view a member in the <strong>Source</strong> <strong>Integrity</strong> Web Interface:<br />

Select a member. From the Project or Sandbox view, choose Member<br />

Commands > View.<br />

To view a revision of a member (not the working file), select a<br />

revision in the Member view and choose View.<br />

To set the default editor in the <strong>Source</strong> <strong>Integrity</strong> Web Interface:<br />

1. From the <strong>Source</strong> <strong>Integrity</strong> Web Interface home page, choose<br />

Configuration.<br />

<strong>The</strong> Configuration <strong>Guide</strong> appears, displaying the current default<br />

editor setting. When <strong>Source</strong> <strong>Integrity</strong> is first installed, it is set to<br />

use Windows Explorer file associations unless you change this<br />

setting.<br />

2. To change this setting, choose Select the default editor.<br />

<strong>The</strong> Select Default Editor page appears.<br />

3. Select the Editor setting and enter or Browse for the editor<br />

application you want to use. Click OK.<br />

When you are satisfied with the changes you have made to a member,<br />

you should check in the member to preserve those changes as a new<br />

revision in the archive. Files should be checked in on a regular basis.<br />

<strong>Source</strong> <strong>Integrity</strong> usually places new revisions at the top of the trunk,<br />

assigning them two-part revision numbers, such as 1.15. <strong>The</strong>re are<br />

times, however, when you do not want your work to be checked into<br />

the trunk. You may be pursuing a line of development that will not be<br />

included in the finished product, for instance, or you may be doing<br />

post-release maintenance while development for the next release<br />

continues on the trunk.<br />

Divergent lines of development in the same archive are managed<br />

through the use of branches. A branch is an independent revision line<br />

that uses an existing revision as its starting point. Members of a<br />

branch revision are identified by their revision numbers. Whereas<br />

<strong>User</strong> <strong>Guide</strong> 87

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

Saved successfully!

Ooh no, something went wrong!