In reply to Scott.

Thanks for these answers, and don't worry, I take all the constructive feedback. In fact this kind of posts in general is really constructive and we need this so Thanks Jeff. (And most of the issues above now have PRs and issues and will get fixed in the next releases).

True that I'm actively involved in Gutenberg, but I'm a contributor like any other contributor, decisions like readiness and APIs are not my own.

Now coming back to my opinion on the API, I feel like you're saying that for an API to be stable, it needs to stop changing? Allow me to disagree with this. For me a stable API is an API that has a good breaking changes strategy. WordPress has a history with avoiding breaking changes and that's good but WordPress also breaks backward compatibility in all releases. Like any software, if you want to stay alive, you need to continue improving it which means breaking existing API. So having a stale API is something that never happens unless the software is dying.

At the moment Gutenberg has an opportunity to make breaking changes quicker than normal in the WordPress world and that's fine and that doesn't mean it's not stable. It's just an opportunity we have to improve and polish things while it's in Plugin Phase, and this will never stop if it stays in Plugin Phase. That doesn't mean the old APIs are not good, it means the new ones are better. After the merge, the pace of these breaking changes will slow down to match WordPress breaking changes pace but I don't think it's going to stop which would mean we stopped evolving WordPress.

> Again, these aren’t problems in themselves. They only start to look like problems because of the urgency that surrounds the project.

I see this over and over again and to be honest, I don't see any urgency myself, Gutenberg (the idea) has been around for several years (mockups in WordCamp US three years ago), the development started more than a year ago (it was in the open from the get go) and the plugin was first released 10 months ago now. As stated several times by the leads, the WordPress 5.0 won't ship until it's ready. I honestly don't see the urgency here.

So we have two options: Get on the Gutenberg train now and help shape the API, which means maybe having to make some small changes to your themes and plugins each 3 Gutenberg releases (and not in urgency because there are deprecating messages etc...) or wait for its final release and hope the API will fit your needs.

When it comes to readiness of Gutenberg: I think it's close to be ready for merge, if you notice the last releases are not as big as the previous ones, we just focus on polishing things essentially. And a lot of this polish can happen after merge like any other part of WordPress, there are still some important bits we have to get int before but these are all known and can land pretty quickly.