Skip to main content

Release communication

Once releases ship weekly rather than quarterly, release comms have to be generated and consistent — not hand-written each time. Produced and approved at the Production Readiness gate.

The rules​

  • SemVer — version numbers mean something; breaking changes are signalled.
  • Changelog — generated from Conventional Commits; every release has one (Keep a Changelog format).
  • Audience-split release notes — the same release, three views:
    • Client — what's new and what it means for them, in plain language.
    • Support — what changed operationally, what to watch, new runbook entries.
    • Internal — the technical detail.

Why it's generated, not written​

At weekly cadence, hand-written release notes are the bottleneck that quietly slows shipping. Generating them from merged changes (with a human approving) keeps releases frequent and the comms consistent. Ties to the rapid-fix SLAs and the client cadence pack.

Standards referenced: Keep a Changelog, SemVer.