Git commit message, changelog, What's New: pick two

[brettcannon]

Do we need three different ways to communicate the same change? This is a somewhat random thought, but I'm wondering if we should consider dropping the changelog for just What's New since it's essentially a more detailed, involved changelog already? That way nothing gets accidentally missed, and anyone who needs the granularity of specific release/tag will have the git commit messages.

[gpshead]

NEWS entries are part of the PR code review and tend to be written in a manner meaningful to users. Version control changelings often are not.

Commit messages can't be reviewed and are often a serial mismash of random on branch commit messages when bots do the message construction and merge.

In the cpython tree, I find them hit or miss. The news entry and the original issue, and even the main branch PR discussion, tend to have more useful context.