[wp-trac] [WordPress Trac] #48870: Include Gutenberg editor enhancments in minor WP updates
WordPress Trac
noreply at wordpress.org
Tue Dec 3 21:50:41 UTC 2019
#48870: Include Gutenberg editor enhancments in minor WP updates
-------------------------+------------------------------
Reporter: knutsp | Owner: (none)
Type: enhancement | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Editor | Version: trunk
Severity: minor | Resolution:
Keywords: 2nd-opinion | Focuses:
-------------------------+------------------------------
Changes (by SergeyBiryukov):
* keywords: close 2nd-opinion needs-patch needs-dev-note needs-docs =>
2nd-opinion
Comment:
Just noting there has been some discussion about this recently on
make/core:
https://make.wordpress.org/core/2019/11/25/devchat-after-the-hour-
november-20/
Per @youknowriad:
> By December 11, Gutenberg will be ahead of Core with about 5 releases
and this is a problem. 12 Gutenberg releases shipped into 5.3 . This is
too much for a single WordPress release and with the current schedule,
it’s seems like this is going to be similar for 5.4… This is not tenable
for the future. It’s hard to stabilize and ship, it’s hard to summarize
the changes for third-party developers and users, it’s more scary to ship
and people were recommending the plugin to be installed for their clients
(and it’s risky since the plugin is a development plugin). So how to
reduce that gap is a big issue that needs solving IMO.Ideally I do think a
shorter release cycle for majors is better. (Why not just a 5.4 in like
end of January 😇 ), otherwise we’ll have to include enhancements in
minors.
These posts might also be relevant:
https://make.wordpress.org/core/2019/11/21/tentative-release-
calendar-2020-2021/
https://make.wordpress.org/core/2019/02/27/major-and-minor-version-
release-cadence/
--
Ticket URL: <https://core.trac.wordpress.org/ticket/48870#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list