Release management with a branch
Use a release branch to preserve the exact state of a shipped release while development continues in the main project.
When to use release management
Use this workflow when you need to support a released version without changing the work in progress for the next version. The release branch provides a stable, auditable record for field issues, regulatory inquiries, and customer change requests.
For example, an automotive supplier can ship certified Advanced Driver Assistance System (ADAS) controller software to an original equipment manufacturer (OEM). The team can maintain the shipped release on a release branch while development continues in the main project.
Workflow summary
The team creates a release branch when the release ships. The team can update the branch for approved support changes, compare the changes with the main project, and merge changes when appropriate. The team can also revert changes and selectively merge specific updates.
The workflow includes release shipment, release branching, continued development in the main project, release-branch updates, change comparison, merging, reverting, selective merging, and branch deletion.
Branching capabilities
Branch Create
Branch Comparison (Diff View)
Branch Merge
Branch Delete