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.I posted this idea about how Coder Upgrade could make it easier for everyone to upgrade their modules to Drupal 8 #1532660: Make Upgrading Modules to D8.2 -> D9 Easier
I do totally understand that there is only so much that code can do to manage this process, but we really need to find ways to do more. Kinda crazy how many Drupal 6 modules still haven't been upgraded a full year and a half after the release of Drupal 7.
Want to start a discussion about how this could be used to streamline the upgrade process & make it easier for all contributors.
Comments
Comment #1
mgiffordChanging the title.
Comment #2
douggreen CreditAttribution: douggreen commentedThis is the holy grail. My first goal is to try to get coder review, coder upgrade, and drupal code sniffer to work together, so that we can write the D8 rules once. Then we need to write the D8 rules. I already have a plan for getting drupal code sniffer integrated, but I don't have one for coder upgrade, partially because I haven't gotten around to tackling that problem yet.
IMO, this is premature, until we can prove that the upgrade works well. Would you like to help with the work in #1745068: Coder Review Drupal 8.x Battleplan.
Comment #3
mgiffordAgreed. It's a long ways off. However, it's something that the Drupal Association (or someone) should consider investing $$ into. The upgrade process for D7 modules is still lagging. It's got to be easier in D8 as we need to have most active modules upgraded within the first year of the stable release of Core.
Comment #4
douggreen CreditAttribution: douggreen commentedSee also #1626420: Meta: get Coder and qa.d.o to work
Comment #5
boombatower CreditAttribution: boombatower commentedThis is something that has been discussed and makes the most sense using the testbot framework (TNG = conduit, job system) to do all the upgrades and either upload or commit to a feature/upgrade branch. The issue is that core does not maintain the actual upgrade routines and they are quite labor intensive to write since they require a lot more effort than reviews.
Comment #6
mgiffordProbably time to start thinking about this again.
Comment #7
mgiffordThe migration of Drupal contrib modules to D7 has been slow. Partly, it's been that there haven't been incentives to do this. But partly it's that folks haven't known how to start.
If we could give people a consistent issue to start with and a link to a Coder Upgrade to start playing with on SimplyTestMe or download to evaluate that would help speed up the process I think.
Realize this is more complicated than this makes it sound.
Comment #8
mgifford