More a reminder than anything else... Once the UI is committed to core:

  1. Move any open and still relevant UI issues to the core queue.
  2. Update the project page accordingly.
  3. The module name will be different (migrate_upgrade vs. drupal_upgrade), so we don't need to pull the UI from the contrib module immediately. We should probably deprecate it in some way, and disable the UI if drupal_upgrade is enabled.

Comments

mikeryan created an issue. See original summary.

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Pittsfield, MA, USA
commented
Priority: Normal » Major

The module name will be different (migrate_upgrade vs. drupal_upgrade), so we don't need to pull the UI from the contrib module immediately. We should probably deprecate it in some way, and disable the UI if drupal_upgrade is enabled.

Actually, what I should do is make a release that's compatible with core 8.0.x only, and cut a branch for >= 8.1.x with the UI removed...

  • mikeryan committed 72aaaf1 on 8.x-1.x 
    Issue #2678382 by mikeryan: With the UI moved to core for Drupal 8.1,...

  • mikeryan committed 72aaaf1 on 8.x-2.x 
    Issue #2678382 by mikeryan: With the UI moved to core for Drupal 8.1,...
  • mikeryan committed d4a2c3f on 8.x-2.x
    Issue #2678382 by mikeryan: Cut 8.x-2.x branch with UI removed.
mikeryan’s picture

mikeryan
he/him
Primary language English
Location Pittsfield, MA, USA
commented
Status: Active » Fixed

All done!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.