Release notes

Write for someone who already uses the product. They want to know what will feel different after they update, and whether they have to do anything. Most read the first line and stop. Some scan the highlights. Few read further. Notes they can scan in seconds beat complete notes they skip.

Gather

• List the changes since the last release, such as with git log --oneline <last tag>..HEAD. Read the PRs and issues they reference.
• Read a change's diff when its commit subject doesn't make the user's experience clear. Describe only effects you can trace to a change.
• Find the project's update steps and the apps or platforms it ships to. Look in its release doc, its README, and the last release's notes.

Shape

In this order: