Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
While working on upgrade documentation I found that there was no documentation that explicitly lists contributed modules that have moved into core. Nor is there a list of modules that have been removed from core.
Spoke with catch on IRC and it was suggested that a section been added to CHANGLOG.txt to keep track of such module additions and deletions.
Comments
Comment #1
dwwDefinitely a good idea.
Not sure if you could consider http://drupal.org/project/plugin_manager moved into core, since what ended up in core is so radically different from that module. ;) Plus, it looks like JoshuaRogers plans to keep developing that for D7 to do stuff like browsing for new projects to install from inside your Drupal site, instead of browsing directly on d.o (seems weird, but hey, that's up to him). ;) That's about the only thing I can think of that I've been personally involved with in D7 core that would count as adding/removing a contrib from core...
Comment #2
sun.core CreditAttribution: sun.core commentedI compiled a full list of modules that have been moved into core, very soon to be committed for http://drupal.org/project/upgrade_status
Not critical though.
Comment #3
andremolnar CreditAttribution: andremolnar commented@sun.core Can you post that full list here. I'll create a patch for the changelog.
By the absolute strictest interpretation of http://drupal.org/node/45111 this may not be critical.
However, not including this documentation could cause someone to go down an upgrade path that would cause heinous complications during an upgrade that would render a site un-useable. For that reason this is quite critical.
Comment #4
andremolnar CreditAttribution: andremolnar commentedTagging as D7 upgrade path since meta issue is closing down.
Comment #5
scor CreditAttribution: scor commentedsee also related #774316: Remind users about new Drupal 8 features after migration from D7
Comment #6
webchickMoving to the right component. Also, this isn't strictly about the upgrade path, so removing tag.
Comment #7
arianek CreditAttribution: arianek commentedbump for jhodgdon while i'm working on the upgrade guide (if anyone knows that this has been done already, pls close!)
Comment #8
jhodgdonBump. This was never added to CHANGELOG.txt.
However, this information is in http://drupal.org/node/895314
and I think it's complex enough that it belongs there and not probably in CHANGELOG.txt. Although we could provide a link -- is it too late to go back and update CHANGELOG.txt for 7.0?
Comment #9
jp.stacey CreditAttribution: jp.stacey at Magnetic Phield commentedAlthough it's in the D7 codebase, this feels to me like basically D6 support: supporting people who are on D6, considering to move to D7.
As D6 is end-of-lifed and hence support is no longer offered; as the policy (enabled by migrate in core) is to move people onto D8 and not D7; as the modules in D8 change gradually anyway (through the "Experimental" list): with all this in mind, I propose this issue is closed as no longer relevant.