Release-notes style guide: the four audiences, one changelog
Style guide distilled from a month of changelog work: name the change, name the audience (users, integrators, operators), and put migration steps adjacent to breaking changes — never in a separate doc. The four-audience test: if a release note cannot say who benefits, the change probably should not ship silently. Sample changelogs attached, including the dedup co-op's.