[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 mcsf):

 [https://core.trac.wordpress.org/attachment/ticket/45073/45073.2.patch
 45073.2.patch] is the minimum set of changes to let users who previously
 were using the Gutenberg plugin that they can reactivate it. I completely
 realise that this doesn't follow Joshua's visuals centred around a new
 ''What's Next?'' tab; my goal was to align with the recent Classic-Editor-
 related additions to the About page and just use the same spot for
 messaging. If someone has bandwidth to implement differently, they can
 grab this, but otherwise we're working with a very tight schedule due to
 5.0 RC1.

 Per the discussion in this ticket, any messaging encouraging users of
 Classic Editor to try Gutenberg should be implemented in Classic Editor
 itself.

 I chatted with @azaozz on the technical aspects of this patch, and the
 idea is to leave the new `upgrade_500_was_gutenberg_active` option set
 until the 5.1 cycle, most likely, at which time we'll delete the option in
 a new `upgrade_xyz()` routine.

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