[wp-trac] [WordPress Trac] #64393: Change how we include Gutenberg in Core

[WordPress Trac]

#64393: Change how we include Gutenberg in Core
------------------------------+--------------------------
 Reporter:  youknowriad       |       Owner:  youknowriad
     Type:  task (blessed)    |      Status:  reopened
 Priority:  high              |   Milestone:  7.0
Component:  Build/Test Tools  |     Version:
 Severity:  blocker           |  Resolution:
 Keywords:  has-patch         |     Focuses:
------------------------------+--------------------------

Comment (by dmsnell):

 we keep mentioning “generated files” but aren’t pretty much //all// of the
 PHP files //except// for a couple manifest files hand-written and
 maintained?

 I don’t mind quarantining built files, but the first breakage I noticed
 was the block parser, something absolutely not auto-generated.

 or should we step back and move all PHP out of Gutenberg and back into
 `wordpress-develop`? I think that would solve a lot of the problems. with
 one source of truth, the PHP repo would be the end-all.

 ----

 last night, after a lot of hassle getting the documentation at
 https://developer.wordpress.org/reference restored (it had been stale for
 over two years), we realized that the build changes break the docs-
 generation again and we will not be able to produce updates for 7.0 until
 we discover how to fix the build process, which is another unknown since
 nobody has worked in these systems since at least August. 2023.

 it could be that any file on the Gutenberg side just disappears from the
 docs, or it could be that those files don’t receive updates. it’s been a
 mess for unrelated reasons, but this makes the mess that much more
 deflating

 solving the mess would have been significantly harder and took much more
 time because I was trying to bisect the changes to find where various
 problems appeared while parsing. all of the new breakage has come from the
 Gutenberg side, so having those extra few minutes to download, install,
 build, and then test while bisecting will be much more heinous in the
 future. at least having potentially-stale copies of those files in Core
 dramatically cuts down the time to find the range of commits in Gutenberg
 where bugs were introduced.

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