In reply to Micha Krapp.

I would add that this decision by Ryan McCue is contrary to all previous statements. In those they had always said that this version would appear only as a core feature. The problem was that, without adoption by a lot of users, it would never be allowed into core. Develop first as a feature plugin is their preferred method, and WP REST API V2 was not not be a plugin.

This decision was news to the WP-API team, for example Rachel Baker has tweeted her surprise, but I think it was the right decision to make. I am closely associated with a development team that has been sitting with idle hands, halfway through a project. The front end has been made, at least in module form, and the back end controls are ready, all we needed was the the API itself. Now we can go full steam ahead, knowing that we will find bugs, report them and see them fixed, by the API team or by ourselves, and we can give ourselves a timescale to full release by the release of WP4.4 in late December.

Until now, the lack of a planned plugin has worried us. It would have delayed us by 6 months, and we would have been less confident of a stable API. By being able to develop with the new API, we can cut the development time by 6 months AND see it stable.