Performancing Metrics

WordPress 2.5 Delayed Until…

I bet you expected me to complete the sentence started in the title of this post, but it is unknown when WordPress 2.5 will be released. The WordPress trac has the due date pushed to the 17th, but some are scratching their heads if that will even happen.

The last full version of WordPress was released September 25th, which means if WordPress 2.5 is released March 25th it will have been a full six months between major releases. That, to me, seems like quite a long time.

While I am prepared to wait as long as it takes for a WordPress release, the one thing I hope is that they will get their timings more exact when it comes to scheduled releases as expectations have been hurt by quite a bit due to this delay.

There is even a whole thread in the support forum discussing the delay, as well as many bloggers expressing their unhappiness at the continued delays, talking about how WordPress 2.4 was skipped, and how WordPress 2.5 continually gets pushed back.

arickrol had this to say:

I do have a question to posit. This is going to come across as a snyde comment so I need to preface this by saying that I do not intend it as such. WP 2.5 has been delayed a week, thankfully it is only a week, but what will keep it from being delayed again?

WP 2.5 is a big release with a lot of work done on it and a lot to do. There are 406 active tickets left to complete according to Milestone 2.5 on Trac. Volunteers can only get so much done in any span of time no matter how dedicated they are. Can they really get 400+ tickets resolved in the remaining 6 days?

While Matt Mullenweg and others have made it clear that any incomplete tickets can just be pushed to the next release, he does pose a good question. How can we trust that WordPress 2.5 will only be delayed a week after the continued delays?

Honestly, we can’t. I guess that means the word for today is patience. At least that means I don’t have to run around upgrading blogs yet.

Categories: WordPress News

This post was written by . You can visit the for a short bio, more posts, and other information about the author.

Comment with Your Facebook Account

Comments

  1. JamieO says: 3/13/2008

    I think I prefer something closer to a six-month release cycle. If there are the necessary interim security patches should the need arise, having to upgrade a product 4 times a year is a little aggressive to me. I understand that there are great ways to improve and grow the product base, but it really puts a pinch on plugin developers, theme developers and designer/developers who use WordPress and include performing upgrades as a part of their basic services. I wonder if the same isn’t true for those contributing code to the release(s)?

    Reply

  2. BN says: 3/14/2008

    Consolidation, consolidation, consolidation!!! The growth of WP was quite “inflationary”, so some consolidation is definitely needed. Yes, I know the desire to overtake yourself on such a successful product is too hard to withstand. But sometimes its better to take a deep breath and give it the time it takes.

    Reply

  3. Trace says: 3/17/2008

    While I am totally prepared to wait for the FREE and exceptional software that is known as wordpress, it is simply bad form for any company to not communicate with its users. It makes WP look a bit disorganized, shows a lack of leadership, creates an environment of rumor and speculation and gives their competition ammo as was the case in Anil’s post last week where he tee’d off of the WordPress non-release….. in short, it is bad form. When you come out and communicate to your users and set realistic expectations that you can execute or even admit a mistake has occurred, you disarm them…. they are much less likely to gripe and become anxious….. plus honest communication is the best policy. A simple “we’ve bitten off a bit more than we can chew with this release and we need an extra week, month, year” would stop all rumors and speculation and soothe users who may be on the anxious side…..

    Reply