Context Navigation

Changes between Version 3 and Version 4 of Ticket #59718, comment 1

-                      v3
+                      v4
 Why is Gutenberg special? Why not enforce that it must fix its incompatibilities like all other plugins? Because Gutenberg is not just a plugin and its code is intended to land in Core. I think of as Core's R&D, an incubator for new ideas that, when ready for the masses, come to Core. Gutenberg and Core are intertwined.
 == The ask from WordPress VIP folks
+== What is the ask that was discussed in Make/Core slack?
 Is there a short-term way to possibly prevent the fatal errors for all ways WordPress Core itself gets upgraded? This includes those upgrade processes that do not use Core's `update_core()`.
+Is there a ''short-term'' way (for 6.4) to possibly prevent the fatal errors for all ways WordPress Core itself gets upgraded? This includes those upgrade processes that do not use Core's `update_core()`.
 What was discussed in the slack thread and thus here in this ticket: