Problem/Motivation
- Rolling a new Drupal core release states that the release manager only needs to add changes to CHANGELOG.txt if "the patch represents a change that people should know about when upgrading".
- The Drupal 8 allowed changes policy restricts changes in patch releases to only non-disruptive bug fixes and documentation improvements.
- The release notes for each patch release are the canonical source for information on the patch release, and as part of the release process are always available at https://www.drupal.org/8/download (which points to the latest Drupal 8 release node).
Proposed resolution
- Add links to https://www.drupal.org/8/download and the change record list to CHANGELOG.txt.
- Clarify the policy that the CHANGELOG.txt will only list significant improvements such as those found in minor and major releases.
- Update CHANGELOG.txt for each minor release.
Original report
I've read Rolling a new Drupal core release which states that the release manager only needs to add changes to CHANGELOG.txt if `the patch represents a change that people should know about when upgrading`.
I would say that all changes should be listed in CHANGELOG.txt, as they were with the 7.x branch, so the developer doesn't have to go searching for a specific release note page on drupal.org to review changes.