In reply to Jeff Chandler.

Riad Benguella - First, looks like you're actively working on GB. Just want to emphasize that any thoughts here should be considered constructive. Now that I'm familiar with React and the GB codebase, I like it. I think the API is elegant. And I'm fairly upbeat about the possibilities of the project as a whole. We have a lot of GB-related development planned.

You asked "What can we do better in this area?"

It's not so much what can be done better. The fact that there are regular API breaking changes just seems to underscore where the project is in the development process. It's not yet fully mature.

This wouldn't be a problem if there wasn't so much urgency to get Gutenberg fully released in core. Based on where it is right now, I'd say even this fall would be optimistic. Ideally, the project needs to get 100% stable first (still a couple months away), and *then* give theme/plugin devs and agencies 3-6 months to adjust.

The other point worth making is that even if the team is announcing deprecations, it's costly and not that fun to have to keep reworking code. And it doesn't make sense to release GB-based code given the still-high probability of future breakage.

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

So if I was going to ask for anything, it would be more clarity (and possibly more reasonable-ness :) ) on what the criteria and timetables are for deciding when GB is 'ready.'

Thanks for the work you're doing on the project.