02.05.2013 Views

User Guide - MKS

User Guide - MKS

User Guide - MKS

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Using a<br />

Resolution CP<br />

Working With a Resolution CP<br />

development path so that it can be incorporated into the next product<br />

release? The Resync CP command is the best option for applying the new<br />

fix.<br />

A PT developer can now create a second change package, 1204:2 for the<br />

same issue. The second change package would include the summary<br />

“Applied fix to main development path”. The PT developer would start<br />

the Resync CP command, select the main development sandbox, and the<br />

first change package—1204:1—in this issue. The second change package—<br />

1204:2—would be used as a resolution change package.<br />

Once all merges have been resolved, the changes are checked into the<br />

resolution change package. The resolution change package is then closed.<br />

The bug fix is now addressed in both the main and variant development<br />

paths, ensuring that the problem is fixed in the Release 2.0a and the next<br />

major product release.<br />

The basic process for resolving conflicts is to apply the target change<br />

package using the Apply CP command. If the Apply CP operation fails<br />

because of a merge conflict, you must then use the Resync CP command to<br />

create a resolution change package. That resolution change package is then<br />

applied to the project using the Apply CP command.<br />

The process involves the following key steps:<br />

Use the Apply CP command to apply a change package to the main<br />

trunk of development.<br />

If Apply CP fails due to a required merge, use the Resync CP<br />

command on the same change package and create a new resolution<br />

change package. Resync CP places the required files, locked, in your<br />

sandbox.<br />

Verify the merges to ensure they are correct.<br />

In your sandbox, check in the members, making sure to associate them<br />

with the newly created resolution change package.<br />

Close the resolution change package.<br />

Apply that resolution change package to the project.<br />

The Apply CP command works directly in the project, adding and<br />

dropping files, and updating file revisions as required to apply the<br />

resolution change package and update the project.<br />

It is important to note that while Resync CP can be used to apply a<br />

resolution change package, the results may not always be acceptable. For<br />

example, if your bug fix is in an existing project member, there would<br />

401

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

Saved successfully!

Ooh no, something went wrong!