Release Management

Release Management is one of the biggest responsibilities for a PO. This starts with the decision process for when to cut a release through monitoring a release and supporting any rollbacks.

This section is split into the stages of a release:

Planning a Release — deciding when to release, picking the version increment, and confirming readiness and the CHANGELOG.
Cutting the Release — version tagging and creating the release branch that deploys to SQA.
Release Tickets & V&V — preparing the V&V report inputs and handing off to the Release Manager.
Automated Production Deployments — PO-initiated production deploys: the deployment window, the manifest.json trigger, safeguards, and rollback.
Monitoring, Rollbacks & Redeploys — watching a release go out, rolling back safely, and config-only redeploys.

The section also covers:

Route Updates — requesting route changes from the HAPS platform team, either separately or as part of a deployment.

New to automated deployments? Read Automated Production Deployments before your first PO-initiated production release. Auto-deploy does not remove the Jira ticket requirement — it changes when the ticket is submitted.