The delirious pace of WordPress 3 development has been delicious!
I’ve enjoyed not being able to keep up at all.
The sprint is on to feature freeze!
There’s going to be a patch sprint of sorts for 3.0 this week. Please grab a ticket, triage, patch or test:http://core.trac.wordpress.org/report/32. The feature freeze is March 1, so everything still on that report in 7 days from now will be punted to a future release.
There are a few incomplete tasks out there that need to get done to finish implementing new features (both small ones on that report, and the major 3.0 features). If you’re interested in helping but aren’t sure where you can, venture over to #wordpress-dev.
Andrew Nacin on wpdevel, Feb 22th, 2010
Jane Wells puts up a “Patches Welcome” sign on a “a handful of small UI enhancement tickets that are low priority for the hardcore devs, but that I’d still like to see make it into 3.0.” Jane will “try to post a couple of pet tickets each day throughout the sprint week that is coming up.”
Better, stronger, faster blog network creation and management will be huge!
Mostly I can’t wait for the twenty ten theme, and the slow death of the (poorly) justified text that may have been the Kubrick themes only shortcoming.
PS. Emphasis above and below (bold) is all mine.
PPS. WordPress 3 will look so good in the title of the next technical book you write 
Wednesday, Feb 23, 2010 Update: Jane has posted “Menus, the Merge, and a Patch Sprint!“ with details on the WordPress Development Blog, including the tidbit that WordPress 3 will have much improved menu management.
I’m certainly looking forward too it. Well, except for having to take new screenshots … and re-doing some screencasts.
Of course Using WordPress … including WordPress 3 does have a nice ring to it…
Although I appreciate the simplicity of the 2010 theme, there are so many more better/cooler/more functional/nicer themes out there which could…and maybe should have been the new default theme.
Good to hear 3.0 is getting done almost, though…
I’d prefer to see all of the 2.9 bugs (mass editing posts,image thumbnail cropping etc…) ironed out before we get a new 3.0 release.
I’ve found that wordpress first releases are never quite stable and tend to wait until .2 or .3 before upgrading unless there is a security patch. I view new releases of wordpress as Beta versions, I have lost count of how many times an upgrade has needed reversing because of a functionality loss.
It is very nice to have new versions and new features but it would be even nicer to have a bug free wordpress that takes a little more time.
I both agree and disagree with that. Usually functionality losses come from plugin incompatibilities with new WordPress versions. That’s not the WordPress Team fault’s but the plugin developers’ fault and frankly, you can’t expect plugin developer to update their plugin the same day a new version of WordPress comes out.
For real commercial and productivity development, I find it better to have different version and subversion of WordPress running and testing all installation and plugins individually and as a whole. That ensures nothing bad happens
Thanks for the headsup!
I’m doing a graduation reserch project about WordPress. Testing the nightlybuilds can give me some cool topics about the upgrades and future features in 3.0.