Quartz 5

Release management models

Properties1
tagsaz-400, module, release, cadence, versioning

2 min read

Release Management Models

MS Learn path: Design and implement a release strategy — deepen module 5.

Overview

Defines what a release is in your organization: the release definition, the cadence you ship on, and the tagging/versioning scheme that names and tracks every artifact so operations and users know what runs where.

Units

  • Release definition and release scope
  • Release cadence (scheduled trains vs on-demand)
  • Tagging/versioning artifacts (semantic versioning, date-based, build ids)

Concepts introduced

Key terms & commands

  • Semantic versioning (semantic-versioning) — Major.Minor.Patch names a release and encodes change severity.
  • Release cadence — the rhythm (weekly, monthly, milestone) of shipping.
  • Tagging (resource-tags) — attach version/build/owner metadata to artifacts and resources for traceability.

Hands-on

Required lab evidence: Define a training release train and SemVer policy, tag a build artifact with the resulting version, and show how the pipeline selects that exact version for release. Delete the test feed/artifact if it has no further purpose.

Exam focus

  • Distinguish a release (a shippable, versioned unit) from a deployment (delivering it to an environment).
  • Cadence answers when; versioning answers what/why; both feed release notes.
  • Tag artifacts/cloud resources for traceability and rollback identification.

release-definition · semantic-versioning · release-strategy · Path MOC

Graph View

Backlinks