In reply to Erick Danzer.

Beat me to it. This bothers me - 5.0 has always been positioned as a "when it's ready" release and it sounds from that phrasing like there's always been a date, at least a rough one, in mind.

Come on, folks - share a roadmap. What major things are left to be done before we have a release? Whats the plan for testing against existing sites and code? What does that include (i.e. will there be testing against sites made with page builders? Which ones? What versions?) Same issue for plugins. What happens to themes that aren't Gutenberg aware? etc... All of this should be on a central, easily seen doc, not scattered in tickets etc.

For that matter, why isn't the same approach as the REST API release being done here? Release a version of core with Gutenberg as a plugin. Let us all download it, test it, catch things, but not use it for sites where there are breaking bugs AND let us deploy it for clients who really will benefit from the new editor. Catch things, fix things, refine things. Do this for a release or two. Then put it in core.

On the React issue - Kudos. Seriously. That reversal was the right thing to do even if not easy and it's great to see it done. I'd like to see Vue but again, a set of requirements for the candidates should be public.