Back in my Windows NT/2000 server admin days, we’d occasionally receive a large package in the mail from our server vendor. Those of us in charge of the servers would set the package down on a table in the break room and eye it with fear and loathing as beads of sweat formed on our brows. For we knew what the package contained - something potentially (and usually) really awful. It was called a “Service Pack.”
A Service Pack was a kind of upgrade that was meant to “correct” and “patch” many problems that Microsoft seemed to feel existed in your currently adequately, painstakingly tuned servers. Of course, it would also install some new goodies that would make life for the Windows admin much, much easier.
Well, the last time I was involved in a Service Pack upgrade, it just broke the entire server. I don’t mean it blue screened or spewed forth some hideous kernel core dumping message. Oh no. I mean the machine stopped working, as in it wouldn’t turn on after the install. I don’t miss those days.
The recent Keeneweb/Wordpress upgrade wasn’t quite so catastrophic, but it sure wasn’t ideal, either. We’ve managed to fix some of the global bugs but there are bound to be others, especially with the visual editor. By all accounts, this upgrade package was poorly developed, and the WP community isn’t happy about it.
But, this is what we have to work with, and hopefully we’ll get most of the bugs worked out as we go forward. So if you see any bad things happening to your site, let us know. We’ll do our best to make it right.
Thanks,
Russ
