background image
<< Using the Tools with UCM | Unifying Code and Content for Web Development >>
Using the Tools with UCM – ClearQuest and ClearCase LT
<< Using the Tools with UCM | Unifying Code and Content for Web Development >>
56
Chapter 4 - Managing Change to Project Artifacts
5
You work with artifacts as usual. You use ClearCase LT in your private workspace
to:
Check out artifacts. When you check out an artifact, ClearCase LT asks which
activity you want to work on. In the background, ClearCase LT keeps track of
the change set (the list of changed artifacts) associated with the activity.
Edit and verify the changes.
Check in the artifacts. When you check in an artifact, it is still part of your
private workspace. Your change does not become publicly available until you
deliver it, as described in Step 6.
6
After you finish work on the activity, you deliver changes for the entire activity (see
Figure 14). Because ClearCase LT keeps track of the change set, you don't have to
specify the list of artifacts to deliver. Delivering the changes makes the changes
publicly available through the integration stream. It can also close the activity,
depending on the policies the project manager has established.
Figure 14
Delivering Changes to the UCM Project Using ClearCase LT
7
After developers deliver a set of activities, the project manager makes a baseline, a
new common starting place for all developers that includes the new activities or
modified artifacts. On your project, a new baseline can be created regularly,
perhaps even daily.
8
If the changes in the baseline are approved (through testing or through another
review process), the project manager promotes it, making it the recommended
baseline.
9
You rebase your development stream (work area) so that when you work on your
next activity, you start from the most recent recommended baseline. Restart with
Step 4 to select the next activity to work on.