If you already run WordPress, then you’ve probably seen the other announcements in your Dashboard about the release of WordPress 2.5. There are plenty of details in the Development Blog posting, so I won’t rehash the feature list here. I’ll just point out a few important details.
First of all, in my post about Release Candidate 1, I mentioned that I had problems with the plugin updater. Since that time, I have been able to upgrade complex plugins with out a problem. [...]
In the interest of getting the word out as quickly and as widely as possible, a brief word about a new WordPress release: If you recently installed version 2.1.1, you should upgrade to WordPress 2.1.2 immediately. There was a security breach on the server which housed the download archives, and some files in the 2.1.1 download were modified to include a serious security hole. There are more details in the official WordPress Dev Blog announcement.
While technically this only affects those who downloaded the 2.1.1 .zip or .tar.gz archives from the wordpress.org site in about the last week, it certainly wouldn’t hurt to go ahead and upgrade, even if you downloaded earlier, or installed from SVN. [...]
All WordPress users are encouraged to upgrade to the newest release, WordPress 2.0.4. The new release contains several important security updates, so you are strongly advised to upgrade. In addition to the security enhancements, there are many other small bug fixes, as well.
What are you waiting for? Download WordPress 2.0.4 now!
A couple of buglets snuck by in the WordPress 2.0.3 release. There should be a version 2.0.4 release relatively soon. But in the meantime, check out the WordPress 2.0.3 Tuneup Plugin, by Mark Jaquith. . [...]
The wee hours of the morning saw the release of WordPress 2.0.3. This release fixes a few bugs that have been identified in the past three months, and it also adds some security enhancements.
If you would like a smaller upgrade package, Mark Jaquith has a zip file that contains just the changed files. It’s unofficial, but I’d trust Mark.
Also, if you don’t regularly check your WordPress Dashboard to see when new releases are available, you can also check the project status on Freshmeat.net. [...]
For those of you who never install “dot-zero” software releases, now is probably a good time to upgrade to WordPress 2.0.1.
All in all we’ve closed 114 bugs in the 2.0.1 release, which you’re welcome to check out if you’re curious about every fix. . [...]
A lot of people are still asking what the differences are between WordPress version 1.5.2 and version 2.0. I did mention that a lot of the differences are under the surface, and I mentioned the WYSIWYG editor and the new user permissions scheme. Rather than list the changes here, I’ll point you to those who have already written about it.
One of the best articles is probably What’s New in WordPress 2.0? over on Owen Winkler’s site. [...]
In response to concerns about availability of support over the Christmas holiday, the release of WordPress 2.0 has been delayed until December 26. This will allow all the fine helpers who answer questions in the forums and on IRC to enjoy the holiday without feeling that they need to rush back to assist upgraders.
Just three hours ago, Matt posted this on the wordpress-hackers mailing list:
Subject: [wp-hackers] 2.0 Release
Wednesday or Thursday, depending on the phase of the moon.
Now would be a great time to start making sure your themes and plugins work with the new version, and post to hackers if you need any help updating them.
Yow! On the one hand, I’m really excited about this release. [...]
WordPress 2.6.2 Release
As most of you have probably already seen in your Dashboard, yesterday afternoon saw the official WordPress 2.6.2 Release. And as mentioned in the comments on my intitial news break on the 2.6.2 Beta, the focus is on two security patches to cover weaknesses in PHP’s random number generation (which affects password encryption strength), and in MySQL’s field length checking. [...]