Highley Recommended, Inc.

NAVIGATIONRELEASE PROCEDURE

CM Home
CM Resources
SCM Policy
Help Requests
Release Procedure
Compatibility Matrix
Online Support
Release Requests

Releasing from Development to DVT:

(Decision to release is made)

  1. Merge the project development branch to the main branch with the assistance of the VOB administrator.
  2. Obsolete the project development branch and all private branches.
  3. Label the main branch with the release label.
  4. Lock the release label.
  5. Build from the release label.
  6. Audit the build to ensure proper content.
  7. Executables are copied from the project development VOB to the release VOB and labeled with release label.
  8. Announce to the Development and DVT teams the release.

Releasing PRs from Development to DVT

  1. PR is reported fixed to configuration manager.
  2. PR files are merged into main branch.
  3. PRs are reviewed by Configuration Manager to ensure they have been moved to the "resolved" state, and the correct build is referenced.
  4. Main branch is labeled with new release label.
  5. PR branch is obsoleted.
  6. Release label is locked.
  7. Build from Release Label
  8. Audit build to ensure correct content.
  9. Executables are copied from the project development VOB to the release VOB and labeled with release label.
  10. Announce to the Development and DVT teams the release.

Releasing from DVT to Customer

See Agile Release Procedures.