[wp-trac] [WordPress Trac] #41316: Introduce "Try Gutenberg" callout

[WordPress Trac]

#41316: Introduce "Try Gutenberg" callout
--------------------------------------------+-----------------------------
 Reporter:  melchoyce                       |       Owner:  pento
     Type:  task (blessed)                  |      Status:  reopened
 Priority:  normal                          |   Milestone:  4.9.6
Component:  Editor                          |     Version:
 Severity:  normal                          |  Resolution:
 Keywords:  has-patch gdpr has-screenshots  |     Focuses:  administration
--------------------------------------------+-----------------------------

Comment (by danielbachhuber):

 I reviewed all 673 open Gutenberg issues today to identify those I think
 are blockers for the `Try Gutenberg` callout:

 * [https://github.com/WordPress/gutenberg/issues/6096 Block conversion
 strips some inline attributes] (and its sibling issues)
 * [https://github.com/WordPress/gutenberg/issues/1586 Adding images to a
 post doesn't also attach it]
 * [https://github.com/WordPress/gutenberg/issues/3900 Gutenberg breaks
 "classic" posts w/ shortcodes by carelessly wrapping shortcodes into <p>
 tags]
 * [https://github.com/WordPress/gutenberg/issues/3656 Editing cases a huge
 number of revisions]

 These are blockers because they cause some amount of data transformation
 that's non-trivial to recover from (particularly if revisions are
 disabled).

 To roll out `Try Gutenberg`, I'd suggest this order of operations:

 1. Resolve all `Try Gutenberg` blockers because it will be very annoying
 to try to fix associated data-mangling at scale after the fact.
 2. Complete the "Feature Complete" milestone by landing all major APIs.
 There's no sense in extensive end-user testing while we're still making
 major architectural changes.
 3. Allocate a solid few weeks to bug-fixing / polish to address the
 usability issues we already know of and don't need reported a second time.
 4. Ensure WordPress.org support forums are adequately staffed, bug
 reporting workflow communicated, etc.
 5. #shipit

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