WordPress 4.8 Release Targeted for June 8

WordPress 4.8 kicked off in this week’s core developer meeting and the schedule for the upcoming release is now published. Beta 1 is scheduled for May 12 and the official release is targeted for June 8. This will be the first major release in 2017 and is focused on laying the foundation for the new Gutenberg editor. The schedule identifies the features that contributors are aiming to ship in 4.8:

  • TinyMCE inline element / link boundaries
  • New media widgets
  • WYSIWYG in text widget
  • WordCamp / meetup dashboard upgrade to the “news” section

Several contributors expressed concern during the meeting about the compressed timeline, as both the beta and RC testing times have roughly half the time they have been given in the past. Also, the release’s close proximity to WordCamp Europe, which officially begins activities the following week, presented additional concerns about the added workload of a release within the May/June timeframe.

“I think people are thinking of this as a normal release, a train leaving the station that a bunch of stuff (multisite! meta!) has to get on to make it in,” 4.8 release lead Matt Mullenweg said. “I agree that needs a much longer timeframe.

“What is really going on is that we have a few simple, already working as plugin enhancements that add a few files, and we want to get those in the hands of users sooner rather than later. We already update TinyMCE all the time. Potential breakage or compatibility should be limited to things that interact with the text widget or the news dashboard module.”

After a brief discussion on the dev meeting notes, the proposed schedule was confirmed. The feature project merge deadline is coming up on May 10, followed by Beta 1 two days later. Any enhancements that are not ready to proceed on this timeline will be put on hold for a future release.


15 responses to “WordPress 4.8 Release Targeted for June 8”

  1. As a theme developer that creates custom buttons to the TinyMCE editor to generate and insert shortcodes, I’m petrified that this update will break many things. Does anyone know that existing themes and plugins won’t break with this update?

      • Thanks for the suggestion Jason, the current nightly builds have none of the new features listed above. Hopefully by Beta 1 the features will be in place so we can tell exactly what’s going on. As a result, for now, as ceasar below suggests, all the custom buttons are working, and hopefully it will stay like that.

    • I’d think page builders would have the toughest time with an inline editor. Most of those may need to disable that functionality, and a lot of them already have inline front end editing built into them.

      • Even though you are never wrong Trevor, I just hope for once you will be this time around. By the end of this week we will get a glimpse more accurately if we need to start panicking again, when we get beta 1 in our hands.

  2. Does WordPress 4.8 plan on being completely compatible with strict Content-Security-Policy headers?
    Currently I have to enable unsafe-inline and unsafe-eval in the script-src part of my CSP or else the Customize feature will not work.

  3. I think that this will be great for user experience. I teach end users, and one of the things that they complain about is the editing of posts and pages. The blocks functionality looks amazing and I think will help overall WordPress adoption. I think it’s a step in the right direction.


Subscribe Via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.