Problem/Motivation
The farm_migrate module that is included with farmOS v2 handles the data migration from farmOS v1 databases. farmOS v1 is no longer officially supported, and we will be upgrading to farmOS v3 (Drupal 10) soon. Continuing to support the migration code from v1 to v3 will mean additional burden to test that it still works and fix anything that might be broken.
Proposed resolution
Instead of continuing to support farmOS v1 migrations, I propose that we deprecate the v1 migrations in the 2.x branch, and remove them in 3.x.
We can provide some documentation for existing v1 users that instructs them to first migrate from v1 to v2, and then upgrade from v2 to v3. There will be no upgrade path directly from v1 to v3.
Remaining tasks
- Add deprecation notices to code.
- Create a change record: https://www.drupal.org/node/3382609
- Open a new task issue to remove deprecated code in 3.x, and document the migration+upgrade process from v1 to v3: #3382616: Remove v1 migrations from farmOS 3.x
User interface changes
None.
API changes
None.
Data model changes
None.
Comments
Comment #2
m.stentaIt might make sense to keep the
farm_migratemodule, and use it as a home for farmOS-specific Migrate API plugins (we may add more for #3382539: farmOS v2 CSV import module...In which case we don't need to deprecate the whole module, just the specific classes and configurations in it that are for the v1 migrations. We can then remove all the v1 migration code in 3.x and add an update hook to uninstall any of the
migrate_plus.migration.*andmigrate_plus.migration.*configuration entities.Comment #3
m.stentaDrafted a CR here: https://www.drupal.org/node/3382609
Comment #4
m.stentaOpened a follow-up issue here: #3382616: Remove v1 migrations from farmOS 3.x
Comment #6
m.stenta