Problem/Motivation
Even after we get the last couple i18n issues resolved, there are still many unknowns and areas for i18n could get improved. Rather than rushing and stating all i18n migrations are ready because we just need to get things out the door, let’s take off the pressure. Give us a little more time to do things properly. Having a separate marking module let’s us mark i18n stable when it is really more stable.
Proposed resolution
- Add a new migrate_drupal_i18n module
- In all i18n source plugins, add to the existing checkRequirements function a call to \Drupal::service(‘module_handler’)->moduleExists(‘migrate_drupal_i18n’).
- If the module doesn’t exist (i.e. it isn’t installed) then it fails requirements and will not be available for migrations.
- Then mark migrate_drupal_i18n as experimental. And mark migrate_drupal as stable.
- Profit
Remaining tasks
- Roll a patch.
- Discuss if this can land as Experimental into 8.5. That way we could mark migrate drupal and the UI as stable sooner.