BMC Helix Release Management policy

A release is a collection of changes and is defined and published by a Forward Schedule of Changes (FSC) during change management. The FSC is a document that lists all approved changes and their planned implementation dates and it is made available in the same maintenance window as the release.

Each release to production requires the execution of the Request for Change (RFC) process. The release management process then creates a release package of approved changes. 

Release environment

A release uses the following environments for each required stage:

    • Development environment (where release is built)
    • Staging environment (where release is tested)
    • Production environment (where release is deployed)


Deployment starts when the Change Manager receives the approved RFC, which allows a release package to be deployed to a target deployment group or environment, such as a business unit, customer group, or service unit.

Upgrades and fixes

Releases can include:

  • Emergency software and hardware fixes
  • Major software releases and hardware upgrades
  • Minor software releases and hardware upgrades

Hotfix deployments are recommended by the BMC Customer Support team. To ensure a timely investigation and response, please open a Case on Support Central > Case Management for a hotfix and/or patch request, not a request for change (RFC).


Different types of releases exist. Each release has its own release identification and is called a release unit. Before the release is made available, it undergoes the following processes:

  • Release testing
  • Release acceptance, which includes testing the backout plans


If release installation does not work as intended, backout plans are initiated by the BMC SaaS Operations team.

Was this page helpful? Yes No Submitting... Thank you