WordPress’s upgrade announcement sounded so dire and urgent (wordpress 2.1.1 dangerous! Upgrade!) that I actually did a manual upgrade myself.

For the first time in my life.

See, I usually upgrade with this nifty one-click process in my control panel thanks to my webhost, but the problem with them is they’re usually slow to get upgrades available, so I’m at their mercy and that’s fine by me. But the word dangerous kept floating around my head so I emailed them asking when they’d get around to putting this one up because the current version is dangerous!!11

They were all, “Do it yourself, whiny.”

Actually they were super nice about it, but that doesn’t suit my storytelling purposes.

So I was like beh, I’ll wait. I can explode my computer with a touch of a mouse, best leave upgrading to easy one-clicks I can blame on someone else for if something goes horrendously wrong. Dangerous? Feh. I’ll live with danger!

But I couldn’t! Because that’s not the way my mind works!

All l I could think was 2.1.1 dangerous! Dangerous! DANGEROUS! My wordpress became a ticking time bomb! A dangerous one!

So I sucked it up, went to the wordpress website, read how to do a manual upgrade, accessed my SQLSLQPHP thingy backed-up my database and upgraded to version 2.1.2 BY MYSELF. When SO MANY THINGS COULD HAVE GONE WRONG simply because I was the one doing the upgrade…

They didn’t.

ILY, wordpress.

But I just wanted everyone should know it was the singularly most terrifying moment of my March so far and maybe if you have any gold stars lying around, well…