Ryan McCue 05:08 on May 25, 2014

1.0 is out! Thanks to…

1.0 is out! Thanks to everyone who helped out with this release and made it the best so far.

That said, progress never halts! We’re working on 1.1 now, and there’s already a heap of issues open. We need to start on a huge documentation and testing push, which @rachelbaker has already started on.

We’ll also have the normal office hours this week; hope to see you there!

Beau Lebens 13:39 on May 25, 2014

Sorry if I’ve completely missed this along the way, but has there been any discussion around versioning? 1.0 wants to never break backwards compatibility, but what happens if (when) something needs to change that isn’t compatible with the current structure? Is there any allowance for somehow passing “?v=2” or something, so that you can then have a different format at some point in the future?
- Ryan McCue 14:17 on May 25, 2014
  
  The plan for versioning, if it’s ever needed, is to use Content-Type headers to indicate the version, much the same way that GitHub versions their APIs. This doesn’t affect the current approach, so it’s not something needed at this point.
  - Beau Lebens 14:52 on May 25, 2014
    
    Ah, interesting. Cool, just wanted to check that it’s something you’d thought about — that’s a neat, “transparent” approach.
rachelbaker 15:08 on May 25, 2014

There is a related post on Make WordPress Core with the full details of the version 1.0 release http://make.wordpress.org/core/2014/05/25/json-rest-api-version-1-0/ including new endpoints for handling users, post_meta, and revisions.