EEdukron DevOps Library
Delivery GovernanceIntermediate11 submodules

Release Management

Coordinate versioning, release branches, change records, approvals, freezes, notes, production deployment, smoke testing, rollback, and hotfixes as one traceable release process.

How this module works

From concept to production evidence

Define scope early, freeze only what risk requires, publish an immutable version, collect proportional approval, execute a timed plan, validate business behavior, and keep rollback and hotfix paths ready.

Learning outcomes

  • Plan and version releases
  • Use release branches and change requests
  • Manage approvals and code freeze
  • Create useful release notes
  • Execute production, smoke, rollback, and hotfix procedures

Flow diagram

Release Management end-to-end flow

Use this sequence as the operating backbone for every submodule note and hands-on exercise.

  1. 01
    Define scopeRelease Management stage 1: define scope with an auditable result before the next stage begins.
  2. 02
    Assign versionRelease Management stage 2: assign version with an auditable result before the next stage begins.
  3. 03
    Prepare branch and changeRelease Management stage 3: prepare branch and change with an auditable result before the next stage begins.
  4. 04
    Approve releaseRelease Management stage 4: approve release with an auditable result before the next stage begins.
  5. 05
    Deploy and smoke testRelease Management stage 5: deploy and smoke test with an auditable result before the next stage begins.
  6. 06
    Close, roll back, or hotfixRelease Management stage 6: close, roll back, or hotfix with an auditable result before the next stage begins.

Integrated hands-on lab

Run a governed production release

  1. Create release scope and version
  2. Prepare change request and notes
  3. Apply approval and freeze criteria
  4. Deploy with smoke tests
  5. Exercise rollback and hotfix path

Complete module contents

11 full submodule notes

Read in order
01

Release planning

Release planning moves a versioned change toward users through repeatable validation, immutable artifacts, controlled promotion, and recoverable release decisions within Release Management. It is not an isolated definition: its value appears when it supports define scope early, freeze only what risk requires, publish an immutable version, collect proportional approval, execute a timed plan, validate business behavior, and keep rollback and hotfix paths ready.

Open full notes
02

Versioning

Versioning provides a concrete platform capability that must be configured, secured, validated, observed, and owned throughout its lifecycle within Release Management. It is not an isolated definition: its value appears when it supports define scope early, freeze only what risk requires, publish an immutable version, collect proportional approval, execute a timed plan, validate business behavior, and keep rollback and hotfix paths ready.

Open full notes
03

Release branches

Release branches moves a versioned change toward users through repeatable validation, immutable artifacts, controlled promotion, and recoverable release decisions within Release Management. It is not an isolated definition: its value appears when it supports define scope early, freeze only what risk requires, publish an immutable version, collect proportional approval, execute a timed plan, validate business behavior, and keep rollback and hotfix paths ready.

Open full notes
04

Change requests

Change requests provides a concrete platform capability that must be configured, secured, validated, observed, and owned throughout its lifecycle within Release Management. It is not an isolated definition: its value appears when it supports define scope early, freeze only what risk requires, publish an immutable version, collect proportional approval, execute a timed plan, validate business behavior, and keep rollback and hotfix paths ready.

Open full notes
05

Approvals

Approvals provides a concrete platform capability that must be configured, secured, validated, observed, and owned throughout its lifecycle within Release Management. It is not an isolated definition: its value appears when it supports define scope early, freeze only what risk requires, publish an immutable version, collect proportional approval, execute a timed plan, validate business behavior, and keep rollback and hotfix paths ready.

Open full notes
06

Code freeze

Code freeze provides a concrete platform capability that must be configured, secured, validated, observed, and owned throughout its lifecycle within Release Management. It is not an isolated definition: its value appears when it supports define scope early, freeze only what risk requires, publish an immutable version, collect proportional approval, execute a timed plan, validate business behavior, and keep rollback and hotfix paths ready.

Open full notes
07

Release notes

Release notes moves a versioned change toward users through repeatable validation, immutable artifacts, controlled promotion, and recoverable release decisions within Release Management. It is not an isolated definition: its value appears when it supports define scope early, freeze only what risk requires, publish an immutable version, collect proportional approval, execute a timed plan, validate business behavior, and keep rollback and hotfix paths ready.

Open full notes
08

Production deployment

Production deployment moves a versioned change toward users through repeatable validation, immutable artifacts, controlled promotion, and recoverable release decisions within Release Management. It is not an isolated definition: its value appears when it supports define scope early, freeze only what risk requires, publish an immutable version, collect proportional approval, execute a timed plan, validate business behavior, and keep rollback and hotfix paths ready.

Open full notes
09

Smoke testing

Smoke testing provides a concrete platform capability that must be configured, secured, validated, observed, and owned throughout its lifecycle within Release Management. It is not an isolated definition: its value appears when it supports define scope early, freeze only what risk requires, publish an immutable version, collect proportional approval, execute a timed plan, validate business behavior, and keep rollback and hotfix paths ready.

Open full notes
10

Rollback

Rollback restores a safe service state while preserving evidence and reducing the chance that mitigation introduces a second failure within Release Management. It is not an isolated definition: its value appears when it supports define scope early, freeze only what risk requires, publish an immutable version, collect proportional approval, execute a timed plan, validate business behavior, and keep rollback and hotfix paths ready.

Open full notes
11

Hotfixes

Hotfixes provides a concrete platform capability that must be configured, secured, validated, observed, and owned throughout its lifecycle within Release Management. It is not an isolated definition: its value appears when it supports define scope early, freeze only what risk requires, publish an immutable version, collect proportional approval, execute a timed plan, validate business behavior, and keep rollback and hotfix paths ready.

Open full notes