Preparing for a new release

About this task

After you have released your application, you will be ready to start on the next release. You will need to complete the following operations:

Procedure

  1. Be sure your role is set to build_mgr.
  2. Add a new release value (see How to modify release values), select the purposes that will be used for the new release, and select the baseline release for the new release. (This determines how the process rules will be set up.)
  3. Update the release values for all incomplete tasks.

    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 task’s release value so that update sees the task as a candidate to be included in your project configuration.

  4. Query for the incomplete tasks with a release value that matches the one you just released and with a state of task_assigned.

    > ccm task -query -releaseccm task -query -release old_release -custom "status=’task_assigned’"

    Your output should look similar to the following:

                   1) Task 42: Add fonts to guilib
                   2) Task 56: Fix rounding error in calculator
  5. Modify the release value for all incomplete tasks you queried for in 4 by using the selection set reference form.

    > ccm task -modify -releaseccm task -modify -release new_release @

  6. Update the release values for all completed tasks not included in the current release.
    1. Find all tasks that are marked for the release, but that were not included in the release.

      > ccm task -query -not_in_releaseccm task -query -not_in_release project

      where project is the top-level project for the release that was just released.

      The results of this query show the following kinds of tasks:

      * 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.)

      * Tasks that were completed for the release, whose associated objects were obsoleted, and don’t need to be a part of the final release. (Ignore these tasks.)

    2. Examine each task in the first group of tasks and update the release.

      > ccm task -modify -releaseccm task -modify -release release

  7. Reuse the integration prep project.
    1. Query for all projects in the integration prep project hierarchy.

      > ccm queryccm query "hierarchy_project_members('project_name-version', '')"

    2. Update the release values for all projects in the integration prep project hierarchy by using the selection set reference form.

      > ccm attr -modifyccm attr -modify release -value new_release @

Results

Note: If the integration prep projects have release-specific versions, such as 4.9_int, you also should update the version values to reflect the new release.

Feedback