Files
Lukasz Lenart b1a7c22969 docs: refine creating-version-notes from the 7.3.0 release run (#1828)
* docs: refine creating-version-notes from the 7.3.0 release run

Seven changes, each from something the 7.3.0 run got wrong or had to invent.

Breaking changes were far too long: the old guidance held up a paragraph-length
example and asked for what replaces the old behaviour, which produces prose the
ticket already carries. It is now one sentence plus the ticket link, whose job is
to tell a reader whether to open the ticket.

Reconciliation knew only "listed" or "dropped", so a ticket resolved Won't Do got
silently dropped. Such tickets now go under a Rejected requests section - not into
a type section, where they would read as delivered. Deprecations get their own
section for the same reason: nothing stops working yet.

Security summaries are no longer reproduced verbatim when the ticket itself names
the bypass or the leak; they are truncated at a clause boundary and the cut is
reported to the release manager.

The GitHub release range is now fixed at source by passing previous_tag_name
rather than generating wrong notes and pruning them, and creating a release that
does not exist yet is covered alongside editing one that does.

Also adds the test-build announcement mail as the closing step, the full page
section order, split verification by set-diff, and the note that content_file is
rejected for paths outside the repository.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

* docs: address the test-build announcement to both dev@ and user@

The recipient list was left as the release manager's call because 6.11.0 went to
dev@ and 7.3.0 to user@. Both were mistakes: the announcement goes to both lists,
Bcc private@. A build announced to one list reaches half the people who could
find a problem while the vote is open.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
2026-08-01 17:20:17 +02:00
..