In D6, we have a custom 'project_project' node type provided by project.module with a bunch of custom (non-CCK) fields stored in {project_projects}. In D7, we have a default node type with some core field instances configured for you. The D7 default node type and fields are currently only created during hook_install(). During a site upgrade from D6 -> D7, we need a DB update to create the right node type, default field instances, and perhaps migrate the data from the D6 tables into the D7 fields. This last step might want migrate.module, or maybe in this case things are simple enough that it could be done directly in hook_update_N().

Project nodes themselves are mostly ported at this point, so I believe this issue can be considered active and someone could start working on this at any time.

Related:
#1549402: Provide a D6 to D7 data migration path for project_issue and comments

Comments

senpai’s picture

senpai commented
Title: Data migration for projects nodes to D7 » Data migration for project nodes to D7
senpai’s picture

senpai commented
Priority: Major » Normal
Issue tags: -project, -drupal.org D7

This issue doesn't specifically affect drupal.org anymore, so I'm untagging it.

hass’s picture

hass commented

Why does this not affect d.o? Does d.o not require the current data to be migrated? Sounds wrong to me.

dww’s picture

dww
we/he/they
commented

Because there's custom (example) data migration code in drupalorg_project module that handles d.o-specific project migration. I wasn't thrilled about it being done this way, but there were two factors:

A) Since d.o is going to have N different node types for the different kinds of projects (so we can support different fields for each, etc), it's not going to be generically useful to all Project* sites as-is.

B) Since d.o is so ridiculously huge, the migration was taking days, and we cut a whole bunch of corners and made assumptions to be able to optimize this and speed up the migration. The whole thing is still taking over 24 hours, but it's much better than it used to be.

So, sadly, d.o is separate and special, and we still need to figure out what/if/how to provide something (perhaps just documentation and example migration code) that other sites can use to migrate to D7...