Make WordPress Core

Changes between Version 2 and Version 3 of Ticket #59166, comment 23


Ignore:
Timestamp:
01/18/2024 05:34:33 PM (13 months ago)
Author:
hellofromTonya
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #59166, comment 23

    v2 v3  
    1212>Expectations: Redesign gets done, ships (in the plugin), and is approved by one of the Core REST API maintainers.
    1313
    14 Combining those expectations together, IMO the Core merge criteria:
     14Combining those expectations together and after discussions in DevChat and with the REST API maintainers, the Core merge criteria:
    1515
    16 * Font Library's REST API design are reviewed and guided by one of the REST API maintainers.
    17 * The feature has already been released in the Gutenberg plugin and is running as default enabled in the plugin with no major issues.
    18 * The feature works and is well tested.
    19 * All the above needs to be done before 6.5 Beta 1 for the Core merge to happen before or by Beta 1.
     16* Font Library's REST API design was reviewed and guided by one of the REST API maintainers during development.
     17* The feature was already released in the Gutenberg plugin and is running as default enabled in the plugin with no major issues.
     18* All the above was done before 6.5 Beta 1.
    2019
    2120The Font Library went into 6.4's beta cycle without a Core commit. For 6.5, I'd suggest returning to the typical workflow of new feature being committed or punted before or by Beta 1.