7.5 Moving Work from a Development Stream

Under normal circumstances, project managers and integrators use baselines to share work between projects. But if you start work on an activity in your development stream and then determine that you cannot complete the work for the current project, we recommend that you move the work to the project in which you intend to complete it. To facilitate the merge process, move the work to the new project as soon as you determine that you cannot complete it in the original project. (The longer you wait to merge the work, the less you may remember about it and the greater the potential for merge conflicts.)

We recommend against working in a development stream that contains activities you do not intend to complete for the current project; doing so may prevent the rebase operation from synchronizing your development stream with the work in the baseline.

To Move Work from a Development Stream to Another Project

1. Get the activity's activity-selector by entering the following command in your development view:

cleartool lsactivity -long -cview

2. Join the project in which you intend to complete the work. (See Chapter 2, Setting Up Work Areas.)

3. Decide whether to add the work to the new project's integration stream or to another development stream in the new project.

4. From your view in the original project, deliver the work to a nondefault target (the stream in the new project in which you intend to complete the work). (See Delivering to a Nondefault Target.)

5. Lock obsolete your development stream for the original project.

6. Remove your development view for the original project.