NEW / 1.4A clearer view of every handoff →

Connection recipe / Development

From merged
to moving.

A release is finished when the next team knows what changed. Bring the human handoff into the release process.

Explore the release record ↗

Illustrative GitHub workflow guide. This template does not install a GitHub App or receive repository events.

RP-103 / Release handoff

One useful release brief.

Trigger
A release is approved for publication
Engineering owner
Sam Rivera
Receiving owner
Jules Martin
Required context
User impact, rollout stage, known limitations, support notes
  1. 01

    Filter the signal.

    Separate a merged change from an approved release. Decide which repositories and release labels should begin the handoff.

  2. 02

    Add the human meaning.

    Sam summarizes the customer impact and known limitations. A commit list is context, not a customer-facing explanation.

  3. 03

    Confirm the receiving team.

    Jules reviews the support notes, asks for missing context, and acknowledges readiness. The handoff closes after that acknowledgment.