Actually, I just upgraded my WordPress from version 2.9.2 to WordPress 3.0 last few weeks although WordPress 3.0 had been released on 17 June 2010. I usually don’t rush to upgrade to the latest version of WordPress unless there are major bugs in old WordPress version. For your info, WordPress version 3.0 has been downloaded nearly 11 million times.
Now, there is the latest WordPress version 3.0.1 which will fix around 54 bugs in WordPress 3.0. I believe this is not the final WordPress version 3 updates because based on previous experiences, WordPress team is dedicated to update the security bugs or programming errors once they find out the solutions. Therefore, I can foresee there are more updates from WordPress 3.
In case you are interested to know what bugs have been fixed in newest version, here’s the list for your reference:
typo in wp-admin/includes/media.php
WordPress does not function on iPad in View (non HTML Mode)
Add custom taxonomy to Pages admin menu
Adding an empty menu object displays theme default menu instead
Typo in class-http.php
WP_User object conditional failures
wp_get_single_post and wp_update_post assume post properties
Remove dead $current_user declaration
$current_user unfounded assumptions
Wrong link on Updates screen
Properly close <img> tag
wp_nav_menu() uses IDs for menu-items preventing re-use on the same page
home link current_page nav menu defect on IIS
Twenty Ten content is shifted to the right in Gecko 1.8 (Firefox 2, Seamonkey 1.x)
Menu Locations should be unregisterable by child themes
sprintf() typo in wpmu_signup_blog_notification_subject and
A few markup errors on Plugins screen
Wrong l10n function in schema.php
Custom menu Widget title not filtered
Update codex link
Bugs in edit-tags and edit columns regarding post_type vars
has_cap() bug when logged in as super-admin
WP3.0 XMLRPC wp.newCategory fails for existing category
admin.php tries to read $plugin_page from the wrong directory
wp_unique_post_slug does not work properly for hierarchical custom posts types
Back compat for pages and categories for the load-$pagenow hook
String not i10n’ed in wp-admin/import.php
Don’t return 404 in backend
‘Message’ box on Menu management page rendered outside <html> tag
turning off site administrators can add users doesn’t work
site-specific theme selection won’t save in upgraded MU installs
PHP 4.4+ and PHP 5.0.5 fails on return/pass by reference
quick-edit works only once for a hierarchical custom post type
Categories can’t be added in Press This
Export Errors, Line 72
Allow disabling alterations to global tables during upgrade.
WordPress MS – wp-admin/ms-sites.php line 200 missing echo
Selected language is displayed incorrectly in Multisite
Twenty Ten: attachment images should be centered
loop in tags url to same url
capital_P_dangit TwentyTen DocBlock
Twenty Ten: new description and stylesheet cleanup
get_post_permalink incorrect documentation and variable name
comments_template() generates bad theme-compat path
posts paging calculation inconsistent
WordPress doesn’t report the currently active theme
Password strength localization
function map_meta_cap does not use the user ID when checking super admin
update_metadata() updates unchanged values
Undefined function get_blog_info()
WP_User constructor not working as expected if called with 2 args
You can get more information from WordPress Trac.
Should I Upgrade To WordPress Version 3.0.1
If you are still using WordPress version 2.9.2, you are advised to upgrade to latest version to avoid some common bugs such as missed schedule posts. Besides that, WordPress Version 3.0 had fixed around 1200 bugs from WordPress 2.9.2. For me, I will not upgrade my blog to Version 3.0.1 now because this is a maintenance release and not major release. For version 3.0.1, the database version (db_version in wp_options) changed.
How to Upgrade and Install WordPress?
Kindly refer to my earlier post on step-by-step instructions to upgrade WordPress.
So, have you upgraded your blog to the latest WordPress version? Kindly share your thoughts.