Matt Mullenweg answered a number of questions during a town hall session at WordCamp Montreal on Sunday (which Joachim Kudish liveblogged brilliantly). The conversation during the session quickly turned to the future of WordPress, specifically what’s on deck for version 3.3 of WordPress. Plans for WordPress 3.3 haven’t come together fully yet, but Mullenweg did say the next version could be the “U” version, focusing on improving the uploader and updates.
It’s not clear just what an update to the uploader would look like yet, though the media system has been on the “maybe” list for improvement the last couple of version releases.
Regarding updates, the goal seems to be to move WordPress toward the Chrome implementation for updates. Google’s Chrome browser updates seamlessly on its own, in the background. Mullenweg would like to see WordPress and plugin updates work the same way.
Automatic updates were first introduced to WordPress in version 2.5, “Brecker”, thought then only for plugins. Version 2.7 “Coltrane” went a step further and brought automatic updates to the WordPress core files themselves. The most recent version release, WordPress 3.2 “Gershwin”, implemented an enhancement that will allow future updates to WordPress to modify only affected files rather than downloading all of the WordPress files and overwriting everything.
The upcoming 3.3 could see an even bigger update to automatic updates, allowing WordPress to update without a prompt or button press, entirely in the background.
Would you be excited for a “U” update focused on the uploader and updates, as described above? What effect do you think seamless background updates will have on the WordPress community, particularly how users view new version releases?