Imagine reading the following update notes in a coming version of WordPress: “We have a number of exciting features for WordPress 5.0. The new Gutenberg editor has replaced TinyMCE and heralded in a new and simpler way to edit any type of content. The Fields API now provides a utilized way for plugins and themes to create fields in the customizer, on any type of content, or in options pages. We also welcome new endpoints in the REST API – which is finally becoming a full-fledged citizen and allow you to build fully JavaScript-based sites.”
Most developers would be very happy to read this changelog. But many also understand that all of this is years into the future. How can we change that?
An ode to WordPress versioning
WordPress 3.7 introduced automatic updates, and while many hardcore developers quickly wanted to find ways to disable them t0 not disrupt finely-tuned deployment systems, there is no doubt that it was a net win in terms of usability and security for the vast majority of people running a WordPress site.
When 3.8 was released, we saw patches to the 3.7 branch to fix vulnerabilities found in 3.8. This is great, as backporting security updates ensures ample
Source: https://managewp.org/articles/14398/wordpress-needs-another-long-term-support-version
source https://williechiu40.wordpress.com/2017/02/15/wordpress-needs-another-long-term-support-version/
No comments:
Post a Comment