Since I more or less work in IT, I get to deal with crap like the y2k change and most recently the day light savings time (DST) change. While this has been known for some time and most software vendors have released DST-specific patches months ago, one of my vendors of overpriced content management software has yet to release a patch. What makes matters worse is that their pending patch is not only a DST-specific patch, but a complete application service pack with
tens if not hundreds of other unrelated fixes. So let me get this straight, I am supposed to:
- install this SP in a dev environment
- verify the DST patch works
- verify all of the other bug "fixes" work (they have a very bad track record)
- deploy this to a test environment for blessing by QA
- deploy this to production during an out of cycle release
Oh, and all of this needs to be completed in less than two weeks?!?! No thanks!
After reading between the lines and talking with a few internal folks, the DST fix in the service pack is a simple JVM upgrade. So, I could put my system at risk and install the SP in a two-week turnaround, or I could simply run a JVM update tool from Sun. Yeah, I choose
this option.
At the end of the day I will be DST compliant, but I am not feeling warm and fuzzy about our software vendor.
Labels: complete crap, content management, work
Dear 
