[wp-trac] [WordPress Trac] #48870: Include Gutenberg editor enhancments in minor WP updates
WordPress Trac
noreply at wordpress.org
Wed Oct 21 13:29:43 UTC 2020
#48870: Include Gutenberg editor enhancments in minor WP updates
-------------------------+----------------------
Reporter: knutsp | Owner: (none)
Type: enhancement | Status: closed
Priority: normal | Milestone:
Component: Editor | Version: 5.4
Severity: minor | Resolution: invalid
Keywords: 2nd-opinion | Focuses:
-------------------------+----------------------
Changes (by desrosj):
* status: new => closed
* resolution: => invalid
* milestone: Awaiting Review =>
Comment:
Hi @knutsp,
Thanks for opening this ticket! I am going to close this out only because
this is a wider discussion that will be better served with wider
discussions elsewhere, not because it is a bad suggestion or idea
(`invalid` is certainly inappropriate as a catch-all resolution here).
The Gutenberg plugin is built and released at a much faster pace than
Core. These releases often include new features being built with the
target timeline of being ready for the next major version of Core. Because
of this, months (and sometimes weeks) after a major release of WordPress,
it becomes almost impossible to cherry pick specific changes to backport
into WordPress Core because they are often interwoven with the new block
editor features that must wait for the next major version of Core.
With the release cadence that has been followed in 2019/2020, it seems
that this has been a bit better, as all changes in Gutenberg are synced
with Core once every 3-4 months.
It's also important to remember that the plugin is not technically always
"Core ready". It's often used as a test bed to try out different ways to
solve various problems. So wholesale syncing is not always appropriate.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/48870#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list