Release Checklists

Run repeatable checks before submitting or shipping.

Stop Relying on Release-Day Memory

Release Checklists gives you a reusable set of checks and a separate record of the results for each release. It's for the work that's easy to forget when you've finally fixed the last bug and just want to ship.

A template describes what you normally check. A checklist records what happened when you ran those checks for a particular version.

Make a Template

Start with the recommended template, create a blank one, or duplicate an existing template for a different type of release.

Give it a clear name and organize its items into categories that match how you work. You might have separate areas for first launch, upgrades, purchases, accessibility, and store preparation.

Write checks with an observable result. "Test settings" is vague; "Change the preferred units, relaunch, and confirm the choice is kept" tells you exactly what to do.

You can edit the wording, reorder categories, and remove items that don't apply.

Run a Checklist

Create a new checklist from the template and name it for the version or build you're preparing. Work your way through the items and mark each as passed, failed, or not applicable.

The progress summary shows how far along you are. Use category notes to jot down what failed, the conditions that caused it, or anything you need to revisit.

A failed check should leave enough information that you can pick it up later without redoing the whole investigation from scratch.

Reuse What You Learn

The Actions menu includes bulk options to mark everything passed or not applicable, or reset the checklist. Use those when they reflect the work you've actually done.

Each release keeps its own results. Update the template when you spot a missing step, then use the improved version for the next checklist.

Keep the process useful rather than enormous. A focused set of checks that you actually run is better than pages of boxes everyone skips.