DST 2007 is the new Y2K
I'm surprised the media hasn't mentioned this, but there's a significant issue with daylight savings time coming up in March. Basically, the federal government chose to extend DST, and now everyone is scrambling to update a wide variety of operating systems and applications to contain the new date range.
This issue is certainly not going to cause the potential catastrophe predicted for the Y2K "bug" (read: lazy programming). But, it could cause headaches.
The frustration here is that vendors/software providers are waiting until the last minute to provide software updates when they've had a year-and-a-half (I believe) to be developing these fixes. In fact, Microsoft is still working on updates for Exchange server, which will be directly effected because of its calendaring functionality. There's a real risk that systems and applications will be missed, or vendor-supplied "fixes" won't function as promised.
At first glance, one might just think, "Oh, this just means that some of my meetings might get screwed up because people have the wrong times." Well, I'd bet this affects much, much more than just simple calendaring applications. Think of interdependent scheduled jobs that run routinely at a set time on different computers, and the effects one box not being properly updated might have on that overall process.
It seems like many vendors have failed to provide timely updates. In fact, one of the vendors I deal with hasn't yet finalized whether they are going to bother with an update for the version of a piece of software I work with. So, I either "let go and let God" provide me with the patch, or forcefully and rapidly upgrade our system. (No, I'm not religious -- the "God" comment is completely sarcastic.)
Furthermore, the federal government is waiting on statistics from the Department of Energy to see if this new DST range has benefits before determining if the DST extension will carry on in future years. So, we may have to go through all this in another year.
