What WordPress 3.6 Developers Could have Done Better

I first blogged about WordPress 3.6 in April. I was extremely excited about the new Post Formats UI and the new theme Twenty Thirteen. At the time there was a month left before the release. Then, things got pushed back a bit which messed with my image formatting. Then, at some point, they decided they would have to remove the Post Formats UI for this release. And then they went silent. Weeks passed; a month passed. When they mentioned Post Formats and the new Multimedia features – embedded video and audio – it sparked a creativity in my brain – a way to use the site that would make use of what was unique about the web rather than just being a public journal. And I haven’t known when I could schedule these posts or even write them because after the Post Formats UI decision, they stopped updating the releases section of the website. Look, I’ve been involved with FLOSS software for about a decade now. I know all about the Release when It’s Done method, aka The Debian Way. It tends to lead to better quality releases (keyword: tends). But it also causes a lot of frustration – hence the reason for the Ubuntu fork. Really, all I wanted (and based on a few comments I’ve seen on the web from people who use WP to make a living – designing or writing training materials) was some communication. I understand that you might not know exactly how long it would take to untangle the Post Formats UI from the code. But an estimate would have been better than nothing.At least we’d know you cared what we think. And that’s just human psychology. It’s the reason why all the theme parks have signs telling you how long the wait is going to be for any particular ride. If you know it’s going to be an hour you aren’t as pissed as if it takes an hour and you had no idea. So next time, keep us in the look, WordPress.