[wp-trac] [WordPress Trac] #57631: Editor: Introducing Browse Mode

[WordPress Trac]

#57631: Editor: Introducing Browse Mode
----------------------------+-----------------------
 Reporter:  priethor        |       Owner:  (none)
     Type:  task (blessed)  |      Status:  assigned
 Priority:  normal          |   Milestone:  6.2
Component:  Editor          |     Version:
 Severity:  normal          |  Resolution:
 Keywords:                  |     Focuses:
----------------------------+-----------------------
Changes (by hellofromTonya):

 * keywords:  close dev-feedback =>
 * type:  feature request => task (blessed)


Comment:

 There is a discussion underway in
 [https://wordpress.slack.com/archives/C18723MQ8/p1675483426505789 in Core
 Slack core-committers channel] for code being copied/merged from Gutenberg
 into Core already being blessed.

 Today is 6.2 Beta 1. Core's handbook is clear about how to handle ALL
 enhancements and features requests before starting Beta 1.

 * [https://make.wordpress.org/core/handbook/about/release-cycle/ How the
 Release Cycle Works]:
 >**Phase 3: Beta.** Betas are released and beta-testers are asked to start
 reporting bugs. No more commits for new enhancements or feature requests
 are allowed for the rest of the release.

 * [https://make.wordpress.org/core/handbook/about/release-cycle/releasing-
 beta-versions/ Releasing Beta and RC Versions]:
 >For Beta releases, ensure that the milestone is cleared of enhancement
 and feature request tickets (e.g., Trac query for 6.1). If there is
 agreement within the release squad that a certain enhancement or feature
 request is critical for the release and thus needs to remain in the
 milestone, its ticket type should be changed to “Task (blessed)”. Also
 ensure with the Editor Tech Lead that enhancements/features merges from
 Gutenberg are similarly either cleared from the milestone or changed to a
 “Task (blessed)”.

 This discussion likely will not get resolved before today's Beta 1 party
 starts.

 I'm setting this new feature to "blessed" as it is planned for 6.2 and has
 already been released in Gutenberg. Its continuation is feature
 refinement. Given the fast iterations and release cycles, it will receive
 more testing, discussion, and feedback through Gutenberg's cycles than in
 Core's beta cycle.

 This "blessed" feature can be revisited once there's resolution to the
 discussion.

 In talking with @priethor, there will be a mixture of PHP code to
 merge/backport and packages to update. This ticket can be the landing
 place to track the feature.

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