Got a Great Idea for WordPress 3.8? Have Your Say

If you’ve got a feature idea for WordPress, get ready to pitch it this week.

Co-founder Matt Mullenweg will host the first planning meeting for WordPress 3.8 on UTC Thursday, 8 August 2013 at 6pm in #wordpress-dev on Freenode.

Matt Mullenweg
Matt Mullenweg is leading development of the “experimental” WordPress 3.8.

Mullenweg himself is leading development on version 3.8, which is planned for release in early December.

In his State of the Word address at WordPress San Francisco, he said the release would be “experimental” and would likely feature the MP6 admin UI plugin and the 2014 theme.

WordPress 3.7 and 3.8 are being developed simultaneously.

Lead core developer Andrew Nacin is leading development on 3.7 along with core contributor Jon Cave. WordPress 3.7 is expected to be released in October.

In two posts at Make WordPress Core, Nacin said he would also host a planning meeting for WordPress 3.7, with the first one planned for UTC Wednesday, 7 August 2013 at 8pm in #wordpress-dev on Freenode.

“Thursday’s meeting is a great time to propose features that you’re interested in working on, keeping in mind they may or may not make it into WordPress 3.8,” Nacin said.

“The major goal of 3.7 is to offer a bit of a ‘reset’.”

“But keep in mind an early December timeline sets up WordPress 3.9 to kick off no later than January. Bring your ideas and thoughts as 3.8 development begins!”

WordPress 3.7 will be a quick “platform-focused” released focusing on stability and security, Nacin said, which will focus on language packs, auto-updates for minor releases and improvements to help strengthen user passwords.

“Beyond that, though, the major goal of 3.7 is to offer a bit of a “reset” — which includes a huge cleanup of Trac,” he said.

“We’re currently at 3,800 open tickets, and we’d like to whittle that down as well as make things more manageable for the future.

Andrew Nacin
Andrew Nacin is leading development of WordPress 3.7.

“That includes reorganizing our Trac components, making it easier to contribute to certain areas of core (rather than, say, drinking from a single Trac firehose), and trying to organize teams around these components.”

For the next two development cycles of WordPress, the core team is moving to a new method of developing core features as plugins first after the ongoing success of MP6, as outlined by Mullenweg in San Francisco.

“This ‘features as plugins’ method will allow teams to conceptualize, design and fully develop features before landing them in core,” Nacin said.

“This removes a lot of the risk of a particular feature introducing uncertainty into a release (see also 3.6, 3.5, 3.4…) and provides ample room for experimentation, testing, and failure.

“As we’ve seen with MP6, the autonomy given to a feature team can also allow for more rapid development. And in a way, 3.7 provides a bit of a buffer while we get this new process off the ground.”

Outside of core, there will also be work on, which Nacin said would include a hosted code reference and developer handbooks.

What are your ideas for WordPress 3.7 and 3.8 features? Tell us in the comments below.

Image credits: Julián SantacruzJohnONolan.

9 Responses

      Raelene Morey

      It’s a possibility, but only if the core guys are happy with it. There wasn’t much love for the results of the last attempt. The Post Formats UI will be developed as a plugin before it’s moved into core.


      Not sure we ever will now. That was a feature of greatest appeal to bloggers, which Matt says is only 6% of users now.

      For the majority using WP as a CMS, Post Formats aren’t a big deal – in fact, most of the time those sites need to create a totally custom post type.


    I’d like to see a “Drafts” link at the upper level of the Dashboard.


    I don’t care about anything except the Media Library. They began work on it with 3.5, then seemed to think that was enough.

    It needs categories, and needs multiple libraries. Categories will make it much easier to find images. I work on a newspaper site and they often re-use images. Finding them is such a pain that categories would fix.

    And in development, I want a separate library for the site’s image assets. A lot of plugins and themes now use the media library for storing these images, and it just junks up the library. Is it a bad practice anyway? Well, that’s worth debating too. Personally, I create a folder for them, and if the plugin or theme pops up the media manager, I use the URL option and type in the URL where I’ve stored the image.


    Related to @chris_howard more media library features needed. For example on an initial installaton for a webshop several images needs to be uploaded with the same SEO info (alt / title / etc) – these will be modified during the setup of course, but initially could be the same. But if I can upload huge number of images (or just index them from a local folder on the webserver) with the same alt / title / other, could be very nice.


    What I really want to see is security by default. I am a firm believer in the idea that wordpress can be used at the enterprise level, but in order for a more robust use of it, we need a more mature security system behind it. For instance, the basics: hiding and renaming of of wp-login.php and wp-admin.php instead of making the average user fiddle with .htaccess to do so. This would prevent hundreds of brute force attacks right off the bat. Another quick one is more management of your database naming. Don’t feel this would be too hard and would prevent sql injections. Something that WordPress seems to be missing less and less is the fact that, if this is going to be considered a full mature CMS construct on which ANYONE (from the developers to the layman) to create on, security needs to be default. ESPECIALLY for the layman. They don’t know any better. And it’s a system that claims to cater to “the average blogger.” WP needs to start reflecting that sentiment.


    What chris_howard said. I often use a plugin for media categories, but I’d really love to see some – any – form of media file organization rolled into core.

Comments are closed.