We're testing the migration of each D6 module manually (with actual D6 and D8 dbs) and in isolation, mostly to identify the dependencies for each one.

I'm tracking progress for now in a Google spreadsheet - anyone can comment. It'll eventually make it to a docs page, but it's easier to manage in the spreadsheet for now: https://docs.google.com/spreadsheets/d/1gqkqZGZ482whJz3qIuU-ueu5pvUrBmyo...

Process:

  • Read the base configuration entity. Look for dependencies. Add them to the migration manifest. To Do: Make a list of the main migration file for each module
  • Run the migration
  • Create an issue and report the results.

Comments

eliza411’s picture

eliza411 commented
Issue summary: View changes
eliza411’s picture

eliza411 commented
Issue summary: View changes
ultimike’s picture

ultimike
Primary language English
Location Florida, USA
commented

I went ahead and tested the "Database Logging" migration - I don't have write access to the spreadsheet, so I just left some comments.

For the "Help" migration - I didn't see any "help"-related config files nor tests.

I thought about running the "Path" migration - first I want to confirm that this is the d6_url_alias.yml one - correct? This _should_ be dependent on lots of other migrations (like the node migration), correct? It didn't have any dependencies listed.

I also tested the search migration - it mostly works - see https://drupal.org/node/2215173

-mike

chx’s picture

chx commented
Status: Active » Closed (works as designed)

These are D7 variables. The migrations were mostly written from the update-to-config calls in D8 and most of the time we haven't separated D6 and D7 variables as that's slightly pointless. It's going to be a lot of fun now to go over those calls again since removed to verify we didn't remove any... We will also need to add defaults now that we support them...

chx’s picture

chx commented
Status: Closed (works as designed) » Active

Sorry, wrong issue.