It's been a breathless past several weeks in Migrateland - with the core committers as a whole focused on trimming the criticals list for Drupal 8 to zero, Angie "webchick" Byron has given quality time to help the Migrate team get unblocked, triggering a flurry of activity. All along I've meant to post a status update, but things have been moving so fast it's been "well, after this next commit..." Let's review where we stand at the moment, as of September 18, 2015.
From the initial decision to replace the traditional update-in-place (update.php) approach to major version upgrades with a migration-based (import into a fresh site) approach, it was made clear that the initial Drupal 8 release would not be blocked on the upgrade path. If the upgrade path was not "ready", Drupal 8.0.0 would release without it and be available for building new sites only. The plan was as Drupal 8 approached RC status the decision would be made over migration support in 8.0.0. That decision has been reached and published. By all means go ahead and read the official policy as well, but tl;dr: the migrate API and the Drupal 6 upgrade path (and possibly the Drupal 7 upgrade path as well) should be part of the Drupal 8.0.0 release, but marked as "Experimental".
A quick update on where the migration-related modules I maintain on Drupal 7 (migrate, migrate_d2d, and wordpress_migrate) stand now, to help set people's expectations of the level of support they can expect in the issue queues. There are two main points:
Well, what with an increase in client work and a move halfway across the country (Somerville Mass to Murphysboro Illinois), I'm afraid I've fallen further behind on the issue queues for migrate, migrate_d2d, and wordpress_migrate. It's been a bit of struggle to triage the queues, so to somewhat automate the which-issue-to-work-on-next process, I'm reducing it to an algorithm (each step of which will be applied to migrate, migrate_d2d, and wordpress_migrate in that order).
At that point, I plan on cutting release candidates for all three modules. Hopefully at that point I'll be able to start doing a better job of responding to new issues as they come in. Hard to say when I'll have a chance to review and respond to older support and feature requests, though, it'll depend on my workload (but of course I'm not the only one in the community capable of helping out with support requests - hint hint).
Edit: Let's keep track of where I am... I'll also note that not all issues will necessarily get committed/closed, there will be some triage as I go along and not everything will make the cut for Migrate 2.6 and the corresponding migrate_d2d/wordpress_migrate releases.
I've subscribed to the Wired print edition for years. I knew they had an iPad edition for a while (being total Apple fanboys), but I've got a Google Nexus 10 tablet. In the latest issue I saw "Get the digital edition of WIRED for your tablet at bit.ly/tabletWIRED (note the all-caps magazine name, which doesn't actually work - you need to go with all lower-case - I'm not even counting that one). Great, I thought, they finally have Android support. Here I pick up with the feedback I attempted to send from http://www.wired.com/about/feedback (clicked under TABLET):
Went to the tablets page on my Nexus, only to find that you support the Kindle Fire but not other Android tablets. Clicked the FAQ link to try to find your excuse, got 404'd. #doublefail
Submitting that gave me a WSOD at https://w1.buysub.com/servlet/Transaction.
Just had to share this major milestone - 10 minutes ago (as I type this, not as I publish it) I performed the first complete* migration of my Drupal 6 site into my Drupal 8 development environment (running the ui_poc branch of the IMP sandbox, plus a few patches to be submitted/committed).
* "Complete" meaning all user accounts, nodes, comments, and files (including image references within nodes) were migrated - plenty of details yet to be worked out.
Here's a shot from the D8 homepage:
Yes, clearly there's a timezone issue to deal with in importing the dates...