And to think, I was just browsing the WordPress Trac repository earlier today looking at their sweet upgrade scripts in /wp-admin/.
Time to upgrade our sites. There are a lot of them. We love WordPress.
It’s new release time. The latest in our venerable 2.0 series, which now counts over 1.2 million downloads, is available for download immediately, and we suggest everyone upgrade as this includes security fixes. We’re breaking the tradition of naming releases after jazz musicians to congratulate Ryan Boren on his new son (and first WP baby) Ronan.
What’s new? We have about 50 or so bugfixes, which you can review on our dev tracker here, mostly minor bug fixes around feeds, custom fields, and internationalization. If you’d like a nitty-gritty view, check out Mark’s blog post on the changes.
Development Blog – WordPress 2.0.5 – Ronan
One response to “WordPress 2.0.5 – Ronan – new release that also includes important security fixes”
Thanks for spreading the word about the update. With the number of people still running older releases, and the major security holes that continue to be closed in each 2.0.x release, it is very important to get everyone off of the older versions. The two biggest reasons to upgrade to 2.0.5, as I see it, are:
1. This is, again, major security release. There was a major hole plugged;
2. If you started your blog with version 2.0 or newer, youâ€™re missing a DB index on the post table and that will slow down your site.
Iâ€™ve provided more detail in a top 5 list on my own site, but you can always look at the official list of all 60 tickets addressed. I use this link to look at it in order of priority.
Please continue to convince your friends and everyone on your blog roll to upgrade, it is important. If any of them are worried about upgrading, Iâ€™ve included a 35 second upgrade script on my site. Itâ€™s been reviewed by the members of the WP-Hackers list. So, it is safe. Iâ€™d post the link here, but Iâ€™m releasing an updated version of it later today and donâ€™t want the old links floating around. Just look at the Code Cave article link I posted above and follow it from there. 35 seconds for multiple blogs beats 20 minutes to do it by hand.