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...
I've been quiet for a while, so some updates.
First off, this site. As part of the IMP initiative to add the Migrate framework to core in Drupal 8, supporting the upgrade process from 6 and 7, I plan on spinning up a Drupal 8 version of this (currently Drupal 6) site and start running migrations from my live site into it. I will also try to increase my frequency of posts here to help provide some more content for that migration - while my more formal and substantive Drupal-related posts will continue to appear on acquia.com, I'll be adding more personal posts (vacation photos! Everyone loves those!) and maybe some lower-bandwidth Drupal commentary (in particular updates on the migration effort for mikeryan.name).
Speaking of IMP (and vacation photos) - I was off on a 2-week vacation with my wife in mid-March, and naturally have been catching up on customer projects since returning, so haven't contributed for a few weeks. chx and team have continued to make great progress, in particular getting a massive update of the sandbox work on the underlying API committed to core. I should be more active in the IMP effort in the coming months.
It's been a good long time, but I will be ramping up the activity here shortly as I work on IMP (Migrate in Drupal 8 core). I'm spending more time in #drupal-contribute and decided to finally go back to Colloquy as my client.