docs: lead release notes with a user-facing overview#190
Merged
Conversation
Release notes opened straight into the technical `### Added` list. Add a "What this means for you" overview at the top of CHANGELOG [Unreleased] — benefit-framed bullets (what a user can now do), before the technical detail — and record it as a convention in release-process.md. The overview becomes the release intro (and, via the notes automation, the first thing readers see on the release page). Co-developed-by: Claude Code v2.1.201 (claude-opus-4-8)
60cbff7 to
fc07f26
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release notes dived straight into the technical
### Addedlist. Add a "What this means for you" overview at the top of CHANGELOG[Unreleased]— benefit-framed bullets (what a user can now do: feed RTL directly, more PDKs with less setup, simulate SoCs with external QSPI PSRAM, profile GPU cosim time) — before the technical detail, and record it as a convention inrelease-process.md. Lands before tagging rc.4 so that cut demonstrates the full notes shape (overview + version-pinned links).