I've found, as many others have, from butter experience that it's
to make more than one major change at a time, if only because it
ten times harder to figure out the cause of glitches that appear.
calendar rollover is a major change imposed from outside, so it
to me not to do anything else at the same time.
By the way, I hate to admit it, but our last-minute testing did
mistakes we had somehow overlooked.
<[login to unmask email] To: [login to unmask email]
Sent by: DB2 Subject: Re: Y2K - What was all the fuss about?
<[login to unmask email]
DB2 Data Base
Yes the fuss about Y2K. Although I agree with all that has been
was the actual last month that anoyed me. We have tested and made
for the past 18 month to ensure that the Y2K project would be a
Why then freeze all changes to the development environment? Why
massive standby effort after we have proved to management about 10
that the project will work? I do think that there was some over
Crying "WOLF" works, like in this case.
However I am glad that it went well and boring. It means that we
From: [login to unmask email] [SMTP:[login to unmask email]
Sent: 02 January 2000 16:40
To: [login to unmask email]
Subject: Y2K - What was all the fuss about?
The best comment I heard about Y2K was in yesterday morning's
all the hype about Y2K, and the apparent lack of any real
from it (so far), January 1, 2000 will long be remembered as the
Bill Gallagher, DBA
Phoenix Home Life
owners of the list can be reached at
[login to unmask email]