Writing useful extension release notes

Lead with operational impact: supported Joomla and PHP versions, migrations, changed defaults, and any action required after installation.

Group fixes by the workflow they affect rather than listing internal class names. Link technical detail separately for integrators.

Call out security changes plainly and give a tested upgrade path. Euphemisms make risk assessment harder.