Posted by eliza411 on January 14, 2014 at 8:05pm
Migration in core, aka IMP, returned to working in the sandbox last week. This is a slightly unusual development so some explanation is in order. The fundamental API and several migrations have been committed to core, establishing that this initiative actually has legs and will happen, but now that that's in place, it makes sense to return day-to-day work to the sandbox because:
- Core committers are (rightly) focused on beta blockers / criticals, so these patches sit around for a while before getting committed
- When the patches sit, they block other migration work
- The API is still young and we could use space and time to flesh it out more before submitting to core where it becomes more "locked down"
- Arguably, the patches will be easier to review as a whole, because then we can test the D6 -> D8 migration itself, and not just piecemeal parts of it.
We will continue to use the core queue for:
- Major adjustments to the migrate API already committed to core
- Bug fixes to the core API
If you have questions, post them to this discussion or find us in IRC in #drupal-contribute.