Jane Wells, an employee of Automattic doing user experience stuff and other related projects posted on the Wordpress.org blog somethings we can expect to see when Wordpress 3.0 is released in May.

After reading the posting, I am very eager to try it out myself. I’m not going to run it on any of my currently established blogs, especially since they are merging the cores of Wordpress and Wordpress MU. This blog currently uses the Multiblog plugin (well, it’s not really a plugin, but rather a script to allow for multiple blogs under 1 WP install). Under this, I have running this blog, my FFXI blog, and my STO blog. But after the official release, I’ll see what kind of modifications I need to make in going from what I currently use to make use of the new feature that will be in version 3.0.

Something else they have said will be a change in menu management. They invited WooThemes to contribute to the core adding their custom navigation. Now, I’ve never been one to purchase a premium wordpress theme (I don’t see a sense in purchasing a theme for WP when WP itself is free), so I don’t know what all is entailed in their menu system. I do hope that the addition doesn’t cause any conflicts in the themes I run on my existing blogs. I really feel for the theme developers if there are major adjustments that need to be made. Below is an image of their navigation admin panel and I’ve included a couple videos that they have on their blog post.

Woo Custom Navigation admin panel

They (Wordpress.org) has changed their feature freeze to March 1st. After such, no more enhancements or features will be added until they go into production for their next build. They will be focusing on squishing bugs and fixing features that made it into version 3.0. Instead of trying to summarize what is happening until the feature freeze, I’ll just include that portion of the blog post below. You can always read the entire posting here.

Okay, so where are we now? The new feature freeze date is on Monday, March 1, 2010. That means that after that date, no more enhancements or features will be added, and we’ll switch gears to focus solely on crushing bugs and fixing up the features that have already made it in. That means we only have a week to try and finish up the many Trac tickets on the 3.0 milestone that either need a patch or have a patch that needs testing. You can help! From now until noon eastern time on March 1 (that’s 17:00 UTC on March 1), head on over to Trac and pitch in. If you hit a wall, hop into the core development channel at #wordpress-dev on irc.freenode.net and hopefully one of the friendly core contributors can give you a push.