After you have released your application, you will be ready to start on the next release. You will need to complete the following operations:
Add a new release (see Creating or copying a release#), select the process that will be used for the new release, and select the baseline release for the new release.
During the development cycle, some tasks are not included for the current release. One way of doing this is by not completing the task. To be able to bring in the task when it is completed during your new release, you will need to update the release value for the task so that update sees the task as a candidate to be included in your project configuration.
In the Query dialog box, enter the following custom query. The following query returns all completed tasks for the given release (task_release) that are not in the latest baseline with the given release (baseline_release) and purpose (baseline_purpose).
is_available_task_of_release(task_release, baseline_release, baseline_purpose)
Further, the latest baseline is selected from all baselines in the test_baseline, published_baseline or released state. For a task to be considered to be in a baseline, it must be included in the update properties of all projects making up that baseline.
The results of the query shows tasks that were completed after the final build for the release, and were incorrectly left tagged for the release. (Tag these tasks for the new release.)
> ccm task -modify -release new_release task_number (5-12, 18, 23, 33-105)
Developers will need to change the release value for the project hierarchy.