Drew Jaynes to Lead WordPress 4.2

photo credit: 10up
photo credit: 10up

WordPress 4.2 development officially kicked off today at the regularly scheduled core development meeting. Andrew Nacin announced that 10up engineer Drew Jaynes will be leading the release.

Jaynes, who has contributed to every major release since 3.3, recently led the initiative to create inline documentation for every hook in WordPress. He will be accompanied by Scott Taylor, who will help guide core feature plugin development for the media and image efforts that will be in motion throughout 2015.

The WordPress core team is planning three releases this year. “At the moment, that looks like one in April, one in August, and one in early December,” Nacin said. He anticipates that the WP REST API will see the light of day in 4.3 or 4.4, due later this year.

Jaynes opened the meeting with discussion on possible candidates for features in 4.2, which are likely to include Press This, Theme Switcher, and Shiny Updates (smoother installation and updating of plugins and themes). The merge deadline for feature plugins is approximately two weeks away.

“In addition to feature plugins, I’d like the general focus to be on polishing up some of our existing UIs in terms of mobile and accessibility wherever we can,” Jaynes said. “Seems like there’s tickets hanging out there we could get some wins on.”

A 4.1.1 maintenance release is on its way this week or possibly early next week. The 4.2 project schedule is now updated with tentative dates for the release. The team is targeting April 8th for the official release, with the first beta planned for the week of February 25th.

Would you like to write for WP Tavern? We are always accepting guest posts from the community and are looking for new contributors. Get in touch with us and let's discuss your ideas.

10 Comments


  1. The link to possible candidates for features in 4.2 requires login to view. Is there a public accessible place to view the possible new features?

    Report


    1. The slack links are available to anybody with a login to the WordPress.org support forums.

      Report


      1. I can’t seem to login with my WP lognin credential.

        Report


      2. You have to use a special “fake” email address that only works for Slack. This is to prevent extraneous numbers of people from overwhelming the service, while keeping the conversation limited and useful.

        See chat.wordpress.org for more information. Hope that helps!

        Report


  2. I hope they put more emphasis on the front end editor.

    Report


  3. you have to work more in security WP issues and to make it lighter for the website download. Thats URGENT. other things are accessory.

    Report


    1. WordPress is as secure as you make it. Follow security best practices and stay informed and updated on plugin issues and you should be fine. A good backup solution goes a long way as well in making sure you stay safe and secure. Nothing is 100% impenetrable but a good backup plan will always have you covered in the event of a breach/attack.

      Report


      1. @George DeLair,

        “WordPress is as secure as you make it.”

        That’s not true. It’s as secure as you make it within the parameters set by WordPress itself.

        I am pretty sure that @ggb’s point is that the developers should be focusing on those parameters. I agree.

        The recent focus on shiny stuff has got us, among other things, Distraction-Free Writing that isn’t distraction free, a nauseating list of plugins every time the user goes to the Add Plugins page, and a new list of things to be removed from the Customizer: all things should have been handled by plugins, at least until there was a broad consensus as to what merited inclusion in core.

        The WordPress community likes to say that WordPress is now not just a blogging platform but a CMS platform too. It would be nice to see development focusing on stuff that reinforced that claim.

        Report


      2. The majority of security issues have come from plugin/theme based exploits. The WordPress core, if setup correctly is fairly secure. Having said that, I do agree that work should be focused on more core improvements and less “shiny stuff”. The problem is in the inherent fact that in large open sourced based projects you can not please everyone with every release. You do make a valid point.

        Report


  4. “the general focus to be on polishing up some of our existing UIs”

    yawn…

    Report

Comments are closed.