WordPress 3.0 has been released: http://wordpress.org/development/2010/06/thelonious/
any early adopters?
So far my experience with Wordpress 3 seems to be pretty good.
Upon further investigation I have found out that there are significant changes to the underlying construction of the script that does justify the full version number upgrade even though 99.9% of people will probably never use the additional options. Apparently WordPress 3.0 is also the next version for those people who were using WordPressMU as well as the multi site functionality has been fully incorporated but is turned off by default. This explains both why they went for a full version number and why the changes are not really noticeable.
Wordpress is going Great, from Simple blogging tools to a complete CMS.
Good Job by the word press team.
But It is still a long way to catch with Joomla and Drupal, in terms of CMS.
I set up another test blog on localhost. It seems this version is 2 animals rolled into one.
At first the folders/files/database looked very similar to 2.9+
But if you put
define(‘WP_ALLOW_MULTISITE’, TRUE);
in the config and set up “network” the database looks like that found in WPMU
I agree, significant enough change to justify a major release.
Now to get testing some more!
I agree there’s a lot of changes. I didn’t watch the video, but going by the paragraph at the thelonious page linked to:
…
Major new features in this release include
- a sexy new default theme called Twenty Ten.
- Theme developers have new APIs that allow them to easily implement custom backgrounds, headers, shortlinks, menus (no more file editing), post types, and taxonomies. (Twenty Ten theme shows all of that off.)
- Developers and network admins will appreciate the long-awaited merge of MU and WordPress, creating the new multi-site functionality which makes it possible to run one blog or ten million from the same installation.
- As a user, you will love the new lighter interface,
- the contextual help on every screen,
- the 1,217 bug fixes and feature enhancements,
- bulk updates so you can upgrade 15 plugins at once with a single click
…
Still with all that, I would have gone to 2.10 if it was me (features and bug fixes aren’t a fundamental change). Definately more than a 2.9.3 but not really a 3.0 IMHO
Not that it matters much I guess, just a little misleading.
It is definitely just a bug fix. For some reason they went with 3.0 instead of 2.10 - presumably because somewhere in the code is treating the version as one number instead of two separated by a dot.
Did you watch the video, where they introduce the new default theme and all the new features?
I’m no expert by any means, but I thought the version numbers were something like:
4.3.5 -> 4.3.6 indicates very minor changes, should present no compatibilty issues
5.3.4 -> 5.4.0 significant changes, but still should be no or very few compatibilty issues
2.9.2 -> 3.0.0 major changes, compatibilty issues likely if not certain.
True, there’s some pretty hefty changes (new default theme, MU) but I really had been hoping they’d get all the PHP 4 cruft out of the Core at last.
Well it is only a bug fix release, not a whole new version.
Can’t wait to upgrade all my themes and plugins soon 
Also I can’t find out how sexy is new default theme called Twenty Ten cause I can’t preview it on WP site
can you view it here snecz? http://2010dev.wordpress.com/
I guess you’re going to wait then Bbolte 
- I think I’ll test drive ver3 this weekend 
No worries snecz :tup: I do really like the new theme - the menu and changing header’s are neat :tup:
bbolte - It was funny
Alex - I know the sensible thing is to wait and follow your advice :tup: I think curiousity will get the better of me - perhaps I’ll set it up locally and play around with it instead!
Looks like its just an incremental bug fix since the prior version was 2.9 - not a new full version update the way the numbering suggests.
Presumably to patch the security holes in 2.9 you should install 3.0 ASAP.
Finally a better default theme, making unique, compatible customization much easier. 
Now I can preview it
I could not see it on wordpress.org site.
Thanks mizwizzy
I always get a bit nervous about upgrading - mostly about plugins breaking (my own and others that I use).
And this is a major version release 
I’ve gotten in the habit of not upgrading on my live site until I’ve tried it on localhost first. If all seems to be well, I do a database backup, deactivate plugins, uninstall the old files (unless it’s only a minor upgrade, then I over-write), upload the new, upgrade the database, reactivate plugins, then test, test, test.
I’m really, really hoping that they’ve decided to stop supporting PHP 4 with this version. It will make working with my plugins easier. I may even drop support for PHP 4 and WordPress 2+ in my plugins after one more version release of them anyway just to slim them down and make them more efficient.
Except for a WSOD scare http://www.sitepoint.com/forums/showthread.php?t=683949 everything seems to have gone OK on my localhost test blog.
I see in the readme
System Requirements
PHP version 4.3 or higher.
MySQL version 4.1.2 or higher.
So they’re still supporting PHP version 4.
On a positive note, this version loses the browser sniffing “browse-happy” BS.
huh, that was weird. guess i should use the preview button more often. 