[727] in ad-lib
possible change in schedule
daemon@ATHENA.MIT.EDU (sbyrd@MIT.EDU)
Wed May 31 10:52:24 1995
From: sbyrd@MIT.EDU
To: ad-cat@MIT.EDU
Date: Wed, 31 May 1995 10:52:06 EDT
------- Forwarded Message
Date: Tue, 30 May 1995 17:24:45 EDT
From: gyoung@MIT.EDU
To: ganderso@MIT.EDU
cc: bog-lib@MIT.EDU, cfollett@MIT.EDU, efinnie@MIT.EDU, sbyrd@MIT.EDU,
perkins@MIT.EDU, ninadm@MIT.EDU, csrobins@MIT.EDU, donnaon@MIT.EDU,
gyoung@MIT.EDU
Subject: Test and Cutover Scheduling
I'm starting to get a bit uncomfortable about the cutover schedule for
Advance. We discussed it at the Test Coordinators meeting today and
have a proposal. A combination of factors is making it too tight for
comfort.
1. The anticipated arrival of the GMA tape on June 13.
2. Anticipated O/S and DBMS upgrade.
3. Testing completion.
Current plan: Testing until June 7. O/S & DBMS upgrade 8-10. Geac GMA
install on 13th. GMA testing until 20th. Live on 21st.
Problems: The big one is the looming June 7 test deadline. The test
coordinators felt that they still had a lot of testing to do on the
current database. We've put records in for cross functional testing
that isn't completed and wouldn't be carried over for final testing.
They felt it was important to finish this phase of the testing before
moving on to the GMA testing. The O/S - DBMS upgrade should be done
before we go live if at all possible. For maximum comfort it should be
done before the GMA tape is downloaded. The other possible (but minor)
problem with how we went live under this scenario was worry about
damaging the GMA database. The other concern is that we wanted to look
at the GMA data as quickly as possible to check its quality.
A Proposal:
1. We postpone the O/S-DBMS upgrade until after the GMA download
testing. That would give us a few more days after June 7 to finish the
current testing regime and allows us to get quickly to the GMA data
checking.
2. We do the GMA download June 13 or earlier if it's available and we
are ready. We test the GMA intensively for approximately a week until
we're satisfied. We expect it'll be right or not. Currently, we're
more worried about the drop-dead bugs we've found and Geac's willingness
to get them fixed in a timely way.
3. We do the O/S-DBMS upgrade around June 20 after the GMA testing.
Then we re-load the GMA data (assuming it's OK). Do our post-GMA catch
up and go live about June 27.
Circ would bear the worst impact of a delay in the Advance live date.
Anita wasn't at the meeting to give us her assessment. This also gives
a little less experience with the new O/S-DBMS. While there aren't
likely to be as many problems with it as with a new Advance release we
couldn't guarantee that there aren't bugs we'd find after the upgrade.
This also presumes that our I/S guy is available later in the month to
do the O/S upgrade. The other possibility would be to do the upgrade
ASAP but that would likely delay our readiness to test the GMA data.
Thinking in Advance...
- -- Grant
------- End of Forwarded Message
