Release Incident Playbook

Release checklists: pre-release and first 30 minutes

Each published incident type has two checklists: a pre-release checklist tied to the test classes that catch it, and a first-30-minutes checklist for detection, containment and rollback. Both download as Markdown.

116 checklists · 416 pre-release items

All checklists

Incident group

58 of 58 entries, alphabetical

Questions

What is a software release checklist?

A release checklist lists the checks to run before a release. On this site each published incident type has a pre-release checklist whose items name a test class, and a first-30-minutes checklist for after detection.

What is a software deployment checklist?

116 checklists cover 58 published incident types; each pre-release item is one verifiable sentence.

Is a deployment checklist still needed if deployment is automated?

Yes. Automated deployment runs the steps; the checklist names what must be verified, such as a migration run against a production-shaped copy or a configuration check per environment.

Does each checklist include a rollback plan?

Every first-30-minutes checklist includes a rollback decision; 417 first-30-minutes items exist across all checklists.

Which test classes do the checklists reference?

configuration and environment tests (74 items), integration tests (72 items), canary and progressive delivery checks (50 items), end-to-end tests (47 items), synthetic monitoring (38 items), load and performance tests (38 items), unit tests (21 items), chaos and resilience tests (21 items), contract tests (20 items), migration tests (18 items), security tests (10 items), compatibility tests (7 items).

Which pipeline stages do the checklists cover?

Pre-release items map to pre-merge and pre-deploy test classes; some map to post-deploy classes such as canary checks and synthetic monitoring.