[wp-trac] [WordPress Trac] #57631: WordPress 6.2 Editor blessing request: Browse Mode

[WordPress Trac]

#57631: WordPress 6.2 Editor blessing request: Browse Mode
----------------------------+------------------------------
 Reporter:  priethor        |       Owner:  hellofromtonya
     Type:  task (blessed)  |      Status:  assigned
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  Editor          |     Version:
 Severity:  normal          |  Resolution:
 Keywords:  close           |     Focuses:
----------------------------+------------------------------
Changes (by azaozz):

 * keywords:   => close


Comment:

 Re-posting here for posterity:

 I'm thinking the descriptions on how/when to use the "blessed" keyword are
 pretty good in the handbook. But perhaps the part about needing "blessed"
 when adding code from Gutenberg may not be needed.

 My understanding is that the code in the Gutenberg repo is part of core.
 It is being released as a plugin every two weeks so new changes can be
 tested fast, much faster than core trunk.

 The requirement for new features and enhancements to be committed to core
 trunk before beta (which is also the effective "feature freeze") are in
 place to ensure they are adequately tested. However this testing can
 happen in the Gutenberg plugin, and it seems it is quite more effective
 there (300k sites are testing!).

 So when committing code to core trunk during beta, there is no reason to
 disallow hew features and enhancements that have already been tested in a
 Gutenberg release. On the opposite, code tested in Gutenberg for a few
 days has most likely been tested by many thousands of users on many
 thousands of sites. I'm afraid that is not the case for testing the core
 trunk during beta.

 As far as I know Browse Mode will be in the next Gutenberg release. In
 that terms thinking this ticket should be closed as the "blessed" keyword
 is not needed for new features when they have been tested in a Gutenberg
 release. There is no reason to disallow adding them during beta.

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