Release readiness checklist

Review scope, build evidence, defects and sign-offs before a release.

Replaces: the release checklist doc and asking around in standup

Fernway Health · Release readiness checklist

Release readiness checklistFernway Health

Ines CalderEngineering managerIC

Checks: 24; Release 3.18.0 at a41c9e2
Passing: 21; On the current revision
Blocking: 1; Required check failed

Owner	Evidence	Updated	Status
Dev Malhotra	staging-migrations #318	Nov 14	Blocking
Jordan Pike	Reset by new revision	Nov 14	Pending
Nadia Brooks	Ran on c27e0f4	Nov 12	Unknown
Ines Calder	1,946 tests, 0 failed	Nov 14	Pass
Ines Calder	14 of 14 issues merged	Nov 14	Pass
Ines Calder	0 open in Linear	Nov 14	Pass
Dev Malhotra	0 new Sentry issues in 24h	Nov 14	Pass
Nadia Brooks	Runbook updated for 3.18	Nov 13	Pass

Showing 8 of 24 checks

Ran today at 10:15 AM

Found a new candidate revision for 3.18.0: a41c9e2, replacing c27e0f4

Migration dry run

Failed on staging · lock timeout on appointments

Blocking

Linear issue, drafted for review

To: Dev Malhotra
Subject: Release 3.18.0 blocked: migration 0142 times out on staging

The migration dry run for release 3.18.0 (a41c9e2) failed on staging in Buildkite staging-migrations #318. Migration 0142_add_visit_status_index timed out after 30 seconds waiting for a lock on the appointments table. The same migration passed in #311 on c27e0f4 on Nov 12. This is a required check, so the release can't go out until a dry run passes on the candidate revision. Building the index concurrently would avoid the table lock. Target release date: Monday, Nov 16.

Required: Yes
Revision: a41c9e2 on release/3.18
Evidence: Buildkite staging-migrations #318, failed after 30s
Failure: Migration 0142_add_visit_status_index timed out waiting for a lock on the appointments table
Last pass: #311 on c27e0f4, Nov 12

History

Nov 14Dry run #318 failed on a41c9e2
Nov 12Dry run #311 passed on c27e0f4

Runs on its own

Refreshes build and issue evidence

Every 15 minutes it pulls the candidate's builds from Buildkite, issues from Linear and errors from Sentry. When the candidate revision changes, it resets the sign-offs and checks tied to the old one.

Waits for you

Deploying, always

It never deploys. A passing build doesn't make a release ready, and someone accountable records the go or no-go decision.

Works with

GitHub
Buildkite
Linear
Jira
Sentry

What it keeps track of

Release candidate: Versionrepositorybranchrevision
Check: Required or optionalsourceownerresultrevision
Evidence: Build runissue or error linkfetched at
Sign-off: Approverrevisiondate
Exception: Ownerrationaleexpiry

Make it yours

More apps like this

All 42 apps