Preparing for a new release

After you have released your application, you are ready to start on the next release.

Procedure

  1. Add new releases.

    Add a new release (see Creating or copying a release). Select the process to be used for the new release, and then select the baseline release for the new release.

  2. Check that the process rules are set up correctly for the new release.
  3. Update the release for all incomplete tasks.

    During the development cycle, some tasks are not included for the current release. One reason that tasks are not included is because the tasks were not completed. To bring in the tasks after they are completed during your new release, update the release value for the tasks. Update then sees the tasks as candidates to be included in your project configuration.

  4. Update the release for all completed tasks not included in the release you released. (Additionally, update the release values for change requests by using Rational® Change.)

    Rational Change Users:

    • Choose a query called What is not in this build?. This Rational Change query shows change requests that are set to the current release, but are not in the build. This query prompts you for specific release information before performing the query.

      OR

      Rational Synergy Users:

    • Start the Query dialog box.

      Click Find > Tasks

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

    • To add required tasks for the release to the appropriate project grouping, see Adding a task to a project grouping.
  5. Reuse the integration testing projects, if you have not created new ones already.
    1. Right-click on the top-level integration testing project and select Properties.
    2. If you put the release in the version, change the version in the Properties dialog box.
    3. Save the changes by clicking OK.

      If the project contains subprojects, the release is copied automatically to the subprojects.

  6. Reuse the system testing project, if you have not created new ones already.
  7. Tell developers to reuse their development projects.

    Developers must change the release value for the project hierarchy.


Feedback