Releases and the roadmap

A release is a versioned milestone — a bucket of work you intend to ship together, like 1.2.0 or 2.0.0. Releases give your product a spine: a clear sequence of what shipped, what’s next, and what each version contains.

The lifecycle

Every release moves through four statuses:

Change status from the release detail view’s status dropdown. Publishing a release records the exact date and time.

Creating a release

Click New release in the Releases view:

1. Enter a version (e.g. 1.2.0).
2. Optionally add a name (e.g. “Search redesign”).
3. Set an optional target ship date.
4. Click Create.

The release detail view

Click any release to see everything it contains:

Description

A markdown editor for the release’s goals and notes — this becomes the release notes document.

Ship checklist

The checklist is the list of things that must be true before the release ships:

• Click Add item to append a checklist entry.
• Tick the checkbox to mark an item done.
• Drag items to reorder.

Progress (done/total) is shown in the checklist header, in the releases list, and in the dashboard progress bar.

Example checklist:

• [ ] All In Progress features moved to Shipped
• [ ] CHANGELOG entry written
• [ ] API documentation updated
• [ ] Smoke test passed on staging
• [ ] Design review sign-off

Features

Features linked to this release are listed with their stage and priority. Click a feature to open its detail view. Use the Link feature dropdown to assign a feature to this release.

Tasks

Tasks associated with this release (via a feature or directly) appear in a table you can filter and edit inline — the release page doubles as a planning board for that milestone.

Related docs

A curated list of workspace docs relevant to this release. Add docs from the library, reorder them with drag-and-drop. Use this to assemble context for AI tasks — open the Context Composer, select the release’s docs, and hand off.

The active release

One release per product can be the active release — the one currently in progress. It appears in the dashboard progress bar, the status line at the bottom, the Today view’s milestone ring, and the Inspector task board.

Mark a release as active by setting its status to In Progress.

Tips

• Use semantic versioning (major.minor.patch) for software, or milestone names (Q3 launch, Beta) for less technical products.
• Keep the checklist short and binary — items should be clearly done or not done.
• Link your plan doc to the release so context is one click away.
• Publish a release as soon as the checklist is complete, then start the next release — the team always has an active milestone.