Population Statistic: Read. React. Repeat.
Saturday, March 18, 2021

A few days ago, I came upon Ajay D’Souza’s guide for upgrading the security features on WordPress 1.5.x installations.

I was a little surprised to find something like this. With the release of WP 2.0 (since upgraded a couple of times, to the current 2.0.2), I’d have thought that further tinkering with previous versions was dead. Not only that, but Ajay mentions the development of a full upgrade release, to 1.5.3.

I haven’t kept up on the latest scuttlebutt over WordPress development. I can’t find anything on the WordPress site (still as disorganized as ever). I know the rollout of 2.0 was anything but universally accepted, but I never figured that enough diehards would hang onto the 1.5 version to warrant divergent efforts.

So, does this represent a full-fledged forking of WP software development? Are we going to see two separate tracks from here on: The official 2.x and the unofficial 1.5.x?

Nothing is surer to sink an open-source project than the confusion caused by two different versions competing for users. I’ve stayed with 1.5, because it’s working for me and I don’t want the inevitable headaches that come with upgrading. And despite the security fears, I’m of the opinion that I’m realistically no more at risk than the codemonkey that downloads each nightly release (there’s always going to be some malware taking potshots, and a current attack has as much chance of hitting your site as an old one). But I accepted that I was holding onto a system that would eventually have to be replaced, and wasn’t counting on anything new being provided. Now, it seems like 1.5 users like me can hang on for something closer to indefinitely.

by Costa Tsiokos, Sat 03/18/2006 12:01:19 PM
Category: Bloggin', Tech | Permalink |

Trackback this entry: Right-click and copy link
3 Feedbacks »
  1. I wouldn’t be surprised to see a WP fork, but the 1.5.3 release is really a follow up for a security release in 2.0.2. There was belief that enough users were hanging onto 1.5.2 and the security issue was genuine enough, that the patch should be released for that version as well. At least that’s the way I understand it.

    Comment by miklb — 03/18/2006 @ 10:13:38 PM

  2. As I understand it, the WordPress.org developers aren’t working on the 1.5.3 release — that’s what makes it “unofficial”.

    I’d think the response from dot-org would be to take care of the security problem by upgrading to 2.0.x, instead of hanging onto a previous version they don’t want to continue support for indefinitely. That simplifies things and kills the forking possiblity.

    Comment by CT — 03/19/2006 @ 11:44:47 AM

  3. […] a little disappointed, because at first, I was thinking that my musings on a real WP forking were coming true. […]

    Pingback by APRIL FORK’S DAY Population Statistic — 04/01/2021 @ 02:32:58 PM

RSS feed for feedback on this post.

Leave a comment


PLEASE NOTE: Various types of comment moderation may be triggered once you hit the "Say It!" button below. Common causes for this are the inclusion of several hyperlinks and/or spam words in the comment field. Please do not hit the "Say It!" button more than once. If you feel your comment is being blocked without cause, feel free to email me about it.