I take version numbers seriously.

When I see a v6.05 or a v4.03 or something like that, I understand it to be a contract between the developer and the client, “this works, and will remain unchanged until I change the number”.

So of course I had to break my own rule!

A bug came up a few hours after ABTheme 4.06 came out. I had caught the bug before and squished it (an annoying CSS issue in Admin under WP 2.5), with the fix added in 4.06.

Unfortunately, that fix disappeared from adding it until releasing it. And since it seemed to affect only Internet Explorer (I work in Firefox), it slipped by me in the last-minute testing. An alert user caught it this morning, and I reentered the patch, and tested on Firefox and IE (and Opera, for good measure).

But the question is, now what? Release a new 4.07 less than 18 hours later? Or roll it into 4.06 and break the unwritten ‘agreement’ between user and developer?

In the end, I decided a small bug like this didn’t warrant the full-scale upgrade. But I do have to notify people, because it IS a change, and now there’s two flavors of 4.06 out there!

However, aside from blog postings, no one has been notified of the release, so it seems suitable to use the same channel to warn of the change. If you’ve downloaded it today, and you’re using WordPress 2.5, just visit and get ABTheme again.

And expect in the future more version numbers, rather than the same one!