[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:  reopened
 Priority:  normal                           |   Milestone:  5.0
Component:  Upgrade/Install                  |     Version:  trunk
 Severity:  normal                           |  Resolution:
 Keywords:  ux-feedback has-patch fixed-5.0  |     Focuses:
---------------------------------------------+-----------------------

Comment (by azaozz):

 Replying to [comment:55 JoshuaWold]:

 Yeah, I'm still a bit "uneasy" about showing the "Learn how to keep using
 the old editor." message at the top. We have a big section about it at the
 bottom. If we keep it, we will also need to update this a bit to not show
 it when the Classic Editor plugin is activated, there is no way to do that
 from the plugin.

 Last screenshot is what can be done from the Classic Editor plugin as a
 notice. It will show regardless of the message about Gutenberg being
 deactivated. Also, as I mentioned before it won't be translated in most
 languages but that may be acceptable at this point.

 > when is the deadline to do so

 Ideally we should be done with all strings (text) before RC. Then they get
 "frozen" so translators have a bit of headstart. We still can tweak a bit
 the HTML, styling, etc. after.

 > Classic editor included in Core, so adjust everything accordingly.

 That wouldn't make big difference imho. If it is distributed in the
 update, the users would still need to activate it, if it's not, they will
 need to install it. Both actions are pretty similar and easily performed.

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