WordPress 2.9.1 is around the corner

I was a bit worried when I foresaw WP 2.9 showing up around Christmas. So much so, in fact, that Semiologic Pro users were prompted to disable core updates until WP 2.9.1. And rightly so: very nasty niggles showed up when it got released.

On the bright side, WP 2.9 might be the shortest lived major WordPress release yet. WP 2.9.1 RC1 is officially in the wild, a mere 10 days after WP 2.9. At the time of writing, 23 bugs were fixed; over half of them were major.

When it gets released, I’ll feel quite comfortable upgrading this site. So should you.

In other news, a large batch of plugin updates are on the way. They’ll be released alongside WP 2.9, so you can upgrade everything at once. As previously noted, nearly all of these updates are optimizations that are related to the coming Semiologic Cache 2.0.

Regarding the new cache plugin, special thanks go to Mark (Golf Guide). He has been doing his very best to break the plugin in the past weeks. I’ll be releasing RC1 in the next few days. I’ll open a forum thread when I do.

To help out with testing at that stage, toggle Bleeding Edge packages under Settings / Semiologic API Key. Be sure to choose a site with moderate importance, rather than a mere test site; the site needs some traffic for the tests to make any sense, but not so much that you cannot afford it to be quirky until we look into it (which can be minutes or hours).

Comments on WordPress 2.9.1 is around the corner Leave a Comment

  1. see #11674. I still think 2.9 needs to stay in beta. I wish it wasn’t this bad, but I can’t avoid the conclusion that the testers are being overwhelmed by unfixed bugs, lack of response, and inadequate testing time. There are also tons of bug reports in the WP forums that aren’t making it into Trac.

  2. So it gets “wontfix”, I waste a bunch of time trying to argue that the bug is (blatantly) valid, and ultimately I stop testing that version because my reports are still being rejected. Now we see clearly that the “Setting Scope” discussion has gone nowhere. WordPress continues with its “Crash & Burn” policy on new patches.

  3. I wasn’t sure. It seems like half of the core staff are open-minded, and the other half are hell-bent on adding new features at the expense of not fixing the features that are broken. They take it as far as rejecting bug reports on new features that are still in beta. Depending how things play out in the field of plugins, there could be substantial momentum building for a 2.8.7 fork.

    I’m still on a heavily-patched copy of 2.8.4, and I’ve just finished a massive plugin called Tag Groups for hierarchical tag management. The odds of it being compatible with the 2.9 branch are close to zero at this point, so I’m going to need a lot of motivation to upgrade that thing.

  4. “It seems like half of the core staff are open-minded, and the other half are hell-bent on adding new features at the expense of not fixing the features that are broken.”

    I think that the more general problem is that we need one or two bug fix/re-engineering releases before we seriously start thinking about adding new features. But I can’t picture that happening any time soon…

  5. I hopen 2.9.1 comes out soon… i always tell everyone i know who uses wordpress (which admittedly isn’t many people) to _never_ upgrade to a brand new major version (2.7, 2.8 etc) and to wait for the X.1 release. This is even more important if you’re a podcaster- i’ve seen some podcasters totally unable to release new episodes because of incompatible plugins.

  6. I’m glad to see Wordpress 2.9.1 released and I’m going to upgrade because I’ve been sufferred with scheduled posts issues since upgrade to 2.9. I hope this time all the big issues will be fixed permanently.

  7. So 2.9.1 is out, and as predicted I ended up not testing the release candidate because there has been no action on my bug reports from previous versions. When bugs don’t get fixed, I don’t waste my time reporting them.

    Working on the critical patches was rewarding because I could see the benefit for the whole community. Maybe this release on a Monday is a sign that the core team has learned from their previous weekend abandonment release.

    I did put my 2 public plugins into a copy of RC1 to make sure they worked. The next step is to re-evaluate my 2.9.2 site upgrade target. I’m starting to wonder if #11145 will be a deal breaker. A broken Save button is considered a critical issue by most sane bloggers.

    • @miqrogroove: I don’t think that #11145 is that much of a deal breaker, to be honest. I think it always has been that way.

      I do agree that the bugs definitely need a lot to be more attention than they currently do, though. But on this front, I’ve lost most of the hopes I had in 2009. Maybe 2010 will prove me wrong? ;-)

  8. Ah I see now that bug does affect the 2.8 branch, even though it was marked 2.9. So it is “only” a critical bug that has gone unfixed for many versions.

Leave a Comment

The images that show near comments are Gravatars.

Support requests should be supported through the Support Page. Thank you.

Fields marked by an asterisk (*) are required.