Postponed on #2922451: [policy no patch] Make it possible to mark plugins as deprecated.

Problem/Motivation

As per prior discussion in #2607524: [meta] Migrations from Drupal 8 to Drupal 8 and Drupal 8 to Drupal 9 we should deprecate Drupal 6 migration sources in Drupal 9 and remove from core in Drupal 10, creating a contributed module so people can keep it up to date if they desire to.

However, this changed at the Migrate Meeting on 2021-10-07, #3240212: [meeting] Migrate Meeting 2021-10-07. The migrate maintainers agreed to deprecate Drupal 6 and Drupal 7 at the same time to avoid the work of dis-entangling them.

Proposed resolution

1. Decide when to deprecate Drupal 6 and Drupal 7 migrations.
2. Create issue to remove them in the Drupal version after that.
3. Create contributed module to host the migrations (to receive the code when its removed from core).
4. Remove any Drupal 6/Drupal7 migrate specific words in dictionary.txt. Refer to #3210694: Ignore i18n-prefixed words in spellcheck for the regex to remove.

Remaining tasks

All of the above.

User interface changes

None.

API changes

APIs exclusively built to support Drupal 6 and Drupal 7 migrations will be deprecated.

Data model changes

None.

Comments

Gábor Hojtsy created an issue. See original summary.

heddn’s picture

heddn
Primary language English
Location Nicaragua
commented

Yeah!!! Sunset some of this migrate code.

catch’s picture

catch
he/him
Primary language English
commented
Status: Active » Postponed

Just a note we should probably mark migrate multilingual stable before we deprecate this code, so that we're deprecating a fully working set. Although in practice it probably doesn't matter. This might be the first time we're deprecating a feature as such rather than an API with a replacement.

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented
Issue summary: View changes

IMHO it is also possible to add the new ones as deprecated out of the gate, but its indeed cleaner to deprecate once stable.

mikelutz’s picture

mikelutz
He/Him
Primary language English
Location Michigan, USA
commented
Issue tags: +Migrate critical

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented
Title: Deprecate Drupal 6 migration sources in Drupal 8 and remove from Drupal 9 to contrib » Deprecate Drupal 6 migration sources in Drupal 9 and remove from Drupal 10 to contrib
Version: 8.9.x-dev » 9.1.x-dev
Issue summary: View changes

This did not happen in Drupal 8 (before 9). Moving to Drupal 9.1. Also marking postponed on #2922451: [policy no patch] Make it possible to mark plugins as deprecated based on my understanding.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

quietone’s picture

quietone commented
Issue summary: View changes

Updated IS in response to 3210694#9.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented
Issue summary: View changes

Updated wrong version number in API changes in issue summary.

quietone’s picture

quietone commented
Title: Deprecate Drupal 6 migration sources in Drupal 9 and remove from Drupal 10 to contrib » Deprecate Drupal 6 and Drupal 7 migrations and move to contrib
Version: 9.3.x-dev » 10.0.x-dev
Issue summary: View changes
Issue tags: -Migrate critical

This was discussed at the Migrate Meeting on 2021-10-07, #3240212: [meeting] Migrate Meeting 2021-10-07. The migrate maintainers present, mikelutz, benjifisher, heddn and myself agree that the Drupal 6 and Drupal 7 migrations should be removed at the same time. We all noted that the source plugins are used for both Drupal 6 and Drupal 7 migrations and it would be better 'all at once' and avoid the extra work of separating them.

If we are not doing this in Drupal 9.x then it is no longer migrate critical. Removing tag and changing version.

Removed the reference to Drupal 9 and Drupal 10 from the title. It would be good to add that back in when we are sure of the versions.

Updated proposed resolution.

quietone’s picture

quietone commented
Status: Postponed » Closed (duplicate)

Deprecating Migrate Drupal was discussed today in #3313883: [meeting] Migrate Meeting 2022-10-13 2100Z. benjifisher, mikelutz, dinarcon and myself were present. We agreed to make a move on this and now that we have a documented policy for removing modules from core I am closing this issue. I am choosing duplicate because the intention is the same as the new issue, #3315257: [meta] Tasks to deprecate Migrate Drupal.