WordPress 2.9 Released

December 19, 2009 at 1:00 AM · 1 comment

in Operations, PHP, Social Software

WordPress 2.9 was released yesterday, and with it comes several new features.

As announced by Matt at the WordPress development blog, WordPress 2.9 has come out of its release candidate status into FCS.

Unlike the previous several “minor” point releases of WordPress, which have been devoted toward security and stability fixes, WordPress 2.9 is intended to bring online new features… in addition to the expected security and stability fixes.

Recommendation for Production/Operations Teams

Of course, a new release like this will probably have a few bugs that may make you think twice before deciding whether to deploy it for production use.

Our recommendation is that you should withhold using this version until your QA or GPL-OSS test group has cleared the software.

Recommendation for Developers

On the other hand, for developers and readers who are savvy in their appreciation (and usage) of WordPress, our recommendation is a bit different. If you have a version of your site where you typically try cutting-edge software, or if you are already using one of the beta or release candidates of WordPress 2.9, congratulations: you will probably already be aware of the stability conditions of the software.

More importantly, you are probably already prepared to deal with any unusual behavior of the version, or you have already made your determination of it. Thus, our recommendation is to continue with your current course of action.

Javamancy Operations

Javamancy will not be upgrading to this latest version at this time; instead, it will be deployed to a few internal cycle beds for closer examination while we interpret some recent integration changes that are specific to our configurations.

Thanks for being patient, folks! Until then, version 2.8.6 will be in circulation for a while longer. :-)

{ 1 trackback }

Complaining About WordPress: Does That Make You a Bad Person? — Javamancy
December 25, 2009 at 4:09 AM

{ 0 comments… add one now }

Leave a Comment

Previous post:

Next post: