About Upgrading Projects for Minor-Minor Versions

This section describes the process for upgrading projects for minor-minor versions, including setting project priorities. Minor-minor versions can include changes to database schema.

Note: For details on understanding whether a version is major, minor, or minor-minor, see  Understanding the Version/Patch Numbering Scheme.

Automatic upgrades for minor-minor versions start when the ALM Server is restarted after installation of the new minor-minor version.

While a project is being upgraded, users cannot access the project.

The automatic upgrade processes projects that meet all of the following criteria:

  • Lab Management projects

  • Projects whose major and minor version are identical to the major and minor version installed on the server, yet whose minor-minor version is less than the minor-minor version installed on the server.

    Example:  

    Assume ALM version 15.25 is installed on the server:

    • Version 15.21, 15.22, 15.23, and 15.24 projects are automatically upgraded.

    • Version 15.25 and 15.26 projects are not automatically upgraded.

    • Version 14.00 projects are not upgraded.

The upgrade processes projects in the following order:

  • Template and Lab Management projects

  • Projects with the highest priority, as set by the user

  • Most active projects

  • Most recent modification date

  • Highest number of users

  1. Before upgrading the minor-minor version on the ALM Server, you can optionally set priorities to determine the order in which projects are upgraded using the Project Update Prioritization dialog box in Site Administration. For user interface details, see Setting Project Priorities for Upgrading Minor-Minor Versions.

  2. Back up the database.

  3. Install the new minor-minor version on the ALM Server by following the instructions:

After the ALM Server is restarted, projects are upgraded automatically according to the defined priorities.