Release Notes
A curated, customer-facing announcement of what changed in a product. In Specsight, drafted from the changes you pick, written in your product’s voice, and published to a public page.
Release notes are the outward-facing counterpart of a changelog: the announcement a team publishes when a release contains something customers should know about. Unlike a changelog, they are curated — not every change belongs in them — and they are written for the people who use the product, not the people who build it.
Most teams write them by hand. Someone reconstructs what shipped by reading tickets or asking engineers, translates it into customer language, and finds somewhere to publish it — which is why release notes are the first thing to slip when releases are frequent. Specsight drafts them instead: pick a time range or a single release, untick the changes not worth announcing, and it writes the notes in your product’s voice — the audience, tone, and house rules you define. You edit the draft, then publish it to a public page anyone can read.
A Digest and Release Notes are drawn from the same record of changes, for two different audiences. The Digest is faithful and unedited — Specsight’s testimony, for your team. Release Notes are curated and voiced — your announcement, for your customers. One instrument, two outputs.
Related terms
- OPERATIONS
Digest
A plain-language summary of what changed in a Project across a chosen time range. Generated on demand or on a schedule, exportable as PDF, and shareable with a link — designed to keep the whole company in the loop.
- SPEC
Changelog
A chronological record of what changed in a product, feature, or scenario over time. In Specsight, one running changelog covers the whole product, filterable down to a single Feature.
- OPERATIONS
Sync
The release-triggered update to a Specsight spec. Fires automatically every time code lands on the tracked branch, touching only the scenarios that release changed.