In reply to KTS915.

Middle ground would be to ship complete pieces of the API in parts. What we have in the current four core objects proposal doesn't fit the bill for merge-readiness, in my opinion.

For instance, I would not consider shipping a posts endpoints, sans metadata support, or sticky/password-protected support to be considered complete.

I think we would go a long way toward establishing developer trust to commit to shipping complete endpoints one at a time or in multiples. If full-featuredness can be assured in incoming individual endpoints – with an eventual goal of "wp-admin parity" (whatever that means) – that would be a good middle-ground approach.