Delivery & Release

Overview

Delivery and release standards require software changes to move from build to release through verified, automated, and reversible practices.

Choose a standard below to read it in full.

A change affecting deployable software is built, tested, and scanned before merge so security and quality issues are identified early.

Each deployable artifact is built once and used unchanged in every environment to which it is promoted.

Planned deployments are automated, repeatable, verified, and recoverable.

A production deployment proceeds in stages that verify the new version before full rollout.

Feature flags decouple deploying code from releasing it.

A release is a deliberate decision distinct from pipeline completion.

Recovery from a failed deployment follows a fast, rehearsed process.