WordPress 2.5.1 – Another Immediate Update Needed! What The Heck?

Written by

wakish wonderz theme

Here’s another breaking news from the WordPress development community:

Version 2.5.1 of WordPress is now available. It includes a number of bug fixes, performance enhancements, and one very important security fix. We recommend everyone update immediately, particularly if your blog has open registration.

By the first line, it may sound (for newbies) as if a new version of WordPress is out. But no! It’s another “fix” and a fix is there to solve bugs which are present in the main version, namely 2.5
I have been observing the trend of each release of the WordPress package. When a version, lets say A.B is out, there is bound to have other “fix” releases in this family, like A.B.1, A.B.2, A.B.3..etc, so in general it’s A.B.x
When they have enough of this bug fixing, they release a new family, more precisely a new “species”, A.C, just like the example of 2.5

(on blogcatalog, when 2.5 was released, I said to someone that you will see such fix release soon enough, but i guess at that time some people might have just laughed.. that’s cool!)

Now, if you have understood what I mean, prepare youself for other releases like, 2.5.2, 2.5.3, 2.5.4…etc This means you will need to update and upgrade your package “x” times per year!

[..] In addition to the security fix, 2.5.1 contains many bug fixes [..]
[..] If you download the entire 2.5.1 release, you will be getting over 70 other fixes. 2.5.1 focuses on fixing the most annoying bugs and improving performance. [..]

For those of you who keep an eye on these frequent releases, you will find certain common things mentioned each time:
1) important security fix
2) many other bug fixes solved (here about 70!)

As per the WordPress team, it’s the culmination of 6 months of work to release the 2.5 species. Then again, they come back with 2.5.1 fix.
But this is getting so stupid and frustrating to each time having to upgrade like this – it’s basically like 3 to 4 updates per year for bloggers using self-hosted wordpress package. Does the development team not care for all this hastle for us?
Why the hell can’t they just take one full year, test it fully and then bring to the world a robust and strong package!!! I starting to be fed up with wordpress..

Anyway, I let you see some more fix releases soon.. enjoy it if you are a big WordPress fanatic! :P



Posted in: Blogging Enhancements

  (7) Responses to "WordPress 2.5.1 – Another Immediate Update Needed! What The Heck? " - Say your part!

  1. 2
    From Wakish   on April 26th, 2008 at 12:13 pm

    Yeah indeed..
    Thanks for being around ameo!

    2
    From Wakish   on April 26th, 2008 at 12:13 pm

    Yeah indeed..
    Thanks for being around ameo!

  2. 4
    From Zhu   on April 27th, 2008 at 8:15 pm

    I think I’ll wait a bit for this one. I just updated to 2.5 a couple of weeks ago and don’t have much time to go through the whole process this week…

    I appreciate that WP takes the time to fix bugs but hey, it’s a hassle.

    4
    From Zhu   on April 27th, 2008 at 8:15 pm

    I think I’ll wait a bit for this one. I just updated to 2.5 a couple of weeks ago and don’t have much time to go through the whole process this week…

    I appreciate that WP takes the time to fix bugs but hey, it’s a hassle.

  3. 6
    From dibusek   on May 14th, 2008 at 11:21 am

    I also feel annoyed just the same, with the updates just all the way around, again, this is indeed a headache for a self hosted WP site. That’s why I decided to take my blog down during the month to have a self checking before publishing it up again.

    6
    From dibusek   on May 14th, 2008 at 11:21 am

    I also feel annoyed just the same, with the updates just all the way around, again, this is indeed a headache for a self hosted WP site. That’s why I decided to take my blog down during the month to have a self checking before publishing it up again.

Use The Form Below To Leave Your Comment(s):

Feel free to use these tags in your comments: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>