Policy on the inclusion of Migrate in Core for 8.0.0

Last updated on
17 May 2017

This documentation is out of date. Help make it current.

When the decision was made at DrupalCon Prague to remove the major version (D6/7 => D8) upgrade path in lieu of using Migrate for major version upgrades, we agreed that we were not going to hold up Drupal 8's release on Migrate being supported.

This document provides clarification around this policy. See original discussion at https://www.drupal.org/node/2313651.

For developers/site builders

Drupal 8.0.0 ships with a migration path from Drupal 6 to Drupal 8, and from Drupal 7 to 8 (in progress), as well as automated test coverage to keep the code maintainable. The migration path is accessible from the contributed Migrate Upgrade module, via both Drush and a UI.

Migrate in core is considered experimental until at least 8.1.0, and "Migrate critical" issues it exposes will not block the release of 8.0.0.

Migrate in the core will be considered release-ready and remove its “Experimental” label in the earliest 8.x minor release possible (e.g. 8.1.0, 8.2.0), once it has:

  1. A complete 6 -> 8 migration path (prioritized first due to D6’s impending end of life)
  2. A UI in core that passes usability/accessibility gates
  3. No remaining “Migrate critical” issues.

Ideally, also a complete 7 -> 8 migration path, but that can individually be marked as “Experimental” if it is not ready in time.

For Core developers

  • The UI can be added to core anytime up to RC1, or in a later minor release (e.g. 8.1.0, 8.2.0).
  • Any critical issues uncovered in the migration path should be filed as "major" priority, with the "Migrate critical" tag.
  • If a core patch you're working on fails a Migrate test, reach out to a Migrate maintainer for help. (For critical issues, in very rare circumstances, and only at core committer discretion, this policy might apply.)