[wp-trac] [WordPress Trac] #45073: Upgrading to 5.0 and handling the Gutenberg plugin

[WordPress Trac]

#45073: Upgrading to 5.0 and handling the Gutenberg plugin
-----------------------------+-----------------------
 Reporter:  mcsf             |       Owner:  mcsf
     Type:  defect (bug)     |      Status:  assigned
 Priority:  normal           |   Milestone:  5.0
Component:  Upgrade/Install  |     Version:  trunk
 Severity:  normal           |  Resolution:
 Keywords:  ux-feedback      |     Focuses:
-----------------------------+-----------------------

Comment (by JoshuaWold):

 Thank you for the great feedback. We also had an extensive discussion on
 [https://wordpress.slack.com/archives/design/p1541012237189000 Slack]
 about this. Based on the feedback, and technical limitations, it looks
 like we need to make the following changes:

 1. The classic editor path shouldn't be considered here, instead that
 should be an issue created and handled over on the Classic Editor repo. As
 such I've crossed it out.
 2. We can't change the update message prior to updating (at least not
 without releasing 4.9.9 to change the way that messaging appears). So all
 the paths will need to be the generic update message, no message can be
 presented ahead of time that the editor is going to change.
 3. The messaging for Classic Editor should be more friendly.

 I've made a few changes based on this feedback, and will attach it below.
 Please let me know something has been missed.

 Thank you!

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/45073#comment:33>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform