The WordPress Gutenberg project assumes that the so-called Linus's Law can find and fix anything and everything:
given enough eyeballs, all bugs are shallow

While it's a a useful metaphor for FLOSS, it's not a software development methodology and is considered flawed as it does not scale in reality.

An expectation that the community of users should/could test and report all the internal bugs and external issues occurring with Gutenberg seems a stretch. And that's just reporting them. Next, every contributor for all the plugins, themes, and WordPress itself would have to respond to those needs. While most interactions will work fine, the potential range is exponential: [Gutenberg] x [WordPress] x [plugins] x [themes]

Jeff indicates that Automattic's own contributions of Jetpack and Edit Flow aren't yet fully compatible with Gutenberg, which is driven by the company's CEO, led by an employee, and teamed by some company staff. If they can't get it quite right, why push such an expectation across an entire ecosystem that now powers some 30% of the web?

Here's a suggestion: Gutenberg should be treated as an Automattic product like Jetpack. It could be developed and housed as a WordPress.com project and then shared with the community to use or ignore. That's how other companies play in the WordPress ecosystem.

Remember the guiding principle of the WordPress.org roadmap:
a regular release schedule every 3-4 months with the features primarily driven by ideas voted on by our users