Release summary
Read the release milestone and the merged pull requests assigned to it. Group the changes by their effect on users, and link each item to its pull request. Describe configuration changes with an example of the previous and current behavior.
List unresolved blockers with their owners and the evidence needed to close them. Keep speculative work out of the release notes. When a pull request has no user impact, record it in the internal engineering summary instead.
Return draft notes and the blocker list for review before publishing a release.