Identify the issues that must be completed before this module can be given a 1.0 release.

Comments

DamienMcKenna created an issue. See original summary.

mikeryan’s picture

The idea had been to move this into core for 8.1, so I hadn't really thought about a full release. I'm not sure how practical 8.1 is - I don't currently have time to invest in migrate_upgrade myself. Anyway, what did you have in mind for a 8.x-1.0 plan - make any essential issues childs of this one? I would see the main things being:

  1. #2568523: Standardize source module discovery mechanism, which depends on core issue #2569805: For Drupal migration, identify the source module
  2. #2505283: Handle import of private files
  3. Tests
DamienMcKenna’s picture

I didn't have anything specifically in mind, I just thought it'd be good to give people a focal point for the inevitable "we won't use anything without a stable release" comments.

Pierre.Vriens’s picture

hey Mike,

I think you may want to add a pointer on this project's homepage to your comment nr 1 here. Preferably with a reviewed version of "... ultimately bring the UI into core (a decision will be made shortly before RC whether it will make it into 8.0.0)" on that page also (I trust you're aware of what happened in Drupal-land on Nov 19 ...). That might help to avoid questions I recently saw about confused users of it.

PS: next time you plan a visit to "the and of beer" (or Manneke Pis), consider contacting me to possibly meet in person (my Hometown is where "Stella" is ... aka Louvain/Leuven). I'd love to share some of my Drupal-areas-of-interest (hint: Chart 2.0 and BI in Drupal, check my profile for details).

mikeryan’s picture

Status: Active » Closed (duplicate)

As part of #2678382: Post-core submission tasks, I will shortly create a 1.0 release of this module, compatible with Drupal 8.0.x, with the UI and drush commands, and also a 2.x branch without the UI which will be compatible with Drupal 8.1.x and beyond.