For the last few months, the WordPress developer community has been moving towards a release of WordPress 5.0. This is the highly anticipated release that will contain the new Gutenberg editing experience. It’s arguably one of the biggest leaps forward in WordPress’ editing experience and its developer experience in this decade. It’s also not done yet, and if we keep striving for its planned November 19th release date, we are setting ourselves up for failure.
Update November 9th: WordPress 5.0 has been moved
Let me begin by stating that I love Gutenberg. It’s the best thing since sliced bread as far as content editing is concerned. I’m writing this post in Gutenberg. I started writing it on my iPhone. It rocks. But it also still has numerous bugs. In fact, the editor broke on me during writing this post and failed to autosave all the contents. Luckily I saw it breaking and copied the paragraphs to an external editor.
Reasons for delaying
There are a two main reasons why the November 19th timeline is in my opinion untenable:
- There are some severe accessibility concerns. While these aren’t new and a few people are working hard on them, I actually think we can get a better handle on fixing them if we push the release back. Right now it looks to me as though keyboard accessibility has regressed in the last few releases of Gutenberg.
- The most important reason: the overall stability of the project isn’t where it needs to be yet. There are so many open issues for the 5.0 milestone that even fixing all the blockers before we’d get to Release Candidate stage next week is going to prove impossible. We have, at time of writing 212 untriaged bugs and 165 issues on the WordPress 5.0 milestone.
People are working hard
The amount of work being done every day right now by the development team is bordering on the insane. Look at the work for the last three days:
I’d normally be happy with this for a week. This is 3 days, also including a Sunday. It’s been like this for a while. I appreciate all these people doing the hard work, but moving this fast only increases the chance of regressions.
When I mentioned earlier today in the WordPress Slack’s #core-editor channel that I think we should push back, the response was pretty positive:
Let’s get this straight: this is in the channel with a large part of the people working on this release. I’m not the first to say this. I hope this post will help the powers that be come to the same conclusion.
Conclusion: push back, and zoom out
All these things considering, my conclusion is simple: we need to push back the release. My preference would be to January. This would allow us to zoom out a bit, prevent regressions and overall, lead to a better product, with finished documentation. Something that’s worthy of the label RC when we decide to stick that on it. Right now, I feel that the beta is more of an alpha, and we’ll end up with an RC that’s more of a beta.
“Poetry is not an expression of the party line. It’s that time of night, lying in bed, thinking what you really think, making the private world public, that’s what the poet does.”Allen Ginsberg, from Ginsberg, a biography