Around the Corner “WordPress 2.9.1”
Yesterday, I was notified that 2.9.1 is around the corner due to some issues that arose because of a addition to the core of WordPress. According to a blog on wordpress.org “Unfortunately, the recent 2.9 release triggered a bug in certain versions of PHP’s curl extension as well. With these versions of curl, scheduled posts and pingbacks are not processed correctly. To fix this problem as well as a handful of other, lesser issues, we are quickly releasing 2.9.1, the first maintenance release of the 2.9 line.”
While reading the support thread I saw responses like “How could you release an upgrade that is obviously this problem-filled?” or “WordPress should have tested 2.9 before releasing it!“.
Each version of WordPress is tested before it’s release to the public. That is what the Beta releases are for as well as the Release Candidates. WordPress 2.9 went through one release candidate version and two beta releases. In fact, before RC1 hit the public, all of the tickets assigned for that version were closed. Each version was tested by anyone who volunteered. There seems to be this notion that there are thousands of WordPress Developers and they should iron out every bug before releasing software to the public. While there are hundreds of WordPress developers submitting patches here and there as well as squashing bugs, not every hosting setup can be tested. This is where the end users come in.
A patch can be found here which is already a part of 2.9.1.
According to Dion Hulse, a long time contributor to the WordPress Project:
“WordPress 2.9 was just released, And several users have run into a bug. Surprising? Not really. There’s one simple reason for this, While thousands of people Test each and every WordPress release, These users are not You.“