Changes between Initial Version and Version 1 of Ticket #57631, comment 4
- Timestamp:
- 02/04/2023 04:30:44 AM (3 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #57631, comment 4
initial v1 1 1 Re-posting here for posterity: 2 2 3 I'm thinking the description son 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.3 I'm thinking the description 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. 4 4 5 5 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. … … 9 9 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. 10 10 11 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 themduring beta.11 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 Browse Mode during beta.