Way to WordPress 4.7: WP REST API Content Endpoints Approved for Merge into 4.7

WP REST API Content Endpoints Approved for Merge into WordPress 4.7

On Monday, October 17, the WP REST API content endpoints were approved for merge into WordPress 4.7. The WP REST API team and WordPress core contributors conditionally approved the content endpoints as a conclusion of a long and impassioned meeting in the WordPress #core Slack channel, a week after the publication of the merge proposal. Since then, Brian Krogsgard published a document with input from the team on how they intend to assess the success of the API.

The conditions included some last minute work from the team on demonstrating how the API can benefit core development. Contributors produced multiple proofs of concept, including leveraging the REST API endpoints for Press this and Quick Draft features.

WordPress core committer Jeremy Felt said, “It seems that the momentum is on the right track to merge and then continue knocking out issues throughout the rest of the cycle as we start testing it as part of core. I’m also pretty excited about the pieces of the admin that are about to start using it with such a short window.  WordPress versions 4.8 and 4.9 have a ton of potential with the API.”

Felt along with the contributors in attendance at the core development meeting unanimously agreed that the team has come together really well, making significant strides to meets the conditions previously identified for merge. After a short few minutes of discussion, WordPress 4.7 release lead Helen Hou-Sandí officially ‘green lighted’ the mergence of WP REST API content endpoints into core.

Code on the GitHub repository will now be frozen and continued development will be managed via WordPress trac. The WP REST API has had 99 contributors on the project to date. The content endpoints identified in the merge proposal will ship with WordPress 4.7 and contributors will focus on authentication for the 4.8 release cycle.

Source: WordPress Tavern

Leave a Reply

Your email address will not be published. Required fields are marked *