Problem/Motivation

Do we really still need to maintain a separate file for changes, when Git does this for us (and drush rn compiles the data for release notes) ?

Drupal core stopped doing this recently. See #2647824-29: [policy and patch] Determine what should go in CHANGELOG.txt for 8.x core releases for details.

There is already more than enough work for module maintainers; let's make their lives easier.

Proposed resolution

Don't track the module changes in the CHANGELOG.txt file. Instead, if there's interest, a placeholder could be used there instead, something like:

* For a full list of fixes in the latest release, visit:
https://www.drupal.org/project/field_group/releases

Remaining tasks

None.

User interface changes

None.

API changes

None.

Data model changes

None.

Release notes snippet

None.

Comments

colan created an issue. See original summary.

swentel’s picture

swentel commented

Mmm yeah, not really a big fan of this either. I use drush rn as well to add it to the release page, so I'm +1 on removing it.

damienmckenna’s picture

damienmckenna
Location TN, USA
commented

Big -1 to this, it's very useful as a site builder to be able to see what the actual changes are between each downloaded version. And it shouldn't take that much effort to maintain.

swentel’s picture

swentel commented
Status: Active » Closed (won't fix)

Ok, works for me. I don't have strong feelings about keeping or removing, and you're right, it doesn't take that much time anyway :)

colan’s picture

colan
he/him
Primary language English
Location Toronto 🇨🇦
commented

Well, we're now at zero, but I don't care enough to keep fighting this. My motivation is that I don't like duplicating data as per DRY. Anyway, point stated. Let's move on.

it's very useful as a site builder to be able to see what the actual changes are between each downloaded version

So is looking at the release notes that were created with `drush rn`. Sigh.