[290] in Athena_Backup_System
Revising our announced schedule
daemon@ATHENA.MIT.EDU (wdc@MIT.EDU)
Thu Jul 18 18:12:21 1996
From: wdc@MIT.EDU
To: athena-backup@MIT.EDU
Cc: wdc@MIT.EDU
Date: Thu, 18 Jul 1996 18:12:11 EDT
I've been revising the ABS web page today.
Here is the timeline we announced in May:
1. Alpha Test of system by Ops: 2/15/96
2. Fill db with large Cell, test and tune performance (delgado) 3/20/96 - 5/15/96
3. Write system test plan (vrt) 5/1/96 - 6/1/96
4. Write system test suite (vrt/delgado) 5/15/96 - 6/15/96
5. Debug items identified by test suite (delgado) 6/1/96 - 7/1/96
6. Write Administrator's guide (dkk/bwmelans) 5/15/96 - 6/15/96
7. Write improved user interface (urop/delgado) 6/1/96 - 8/1/96
8. Write Migration Plan (bwmelans/dkk) 6/15/96 - 7/15/96
Here are the things we said we needed to enter Beta:
jis OK's Requirements
System passes test suite
Administrator's Guide written, reviewed, and accepted
Code review complete
Performance OK
measure current time make sure we're not worse
preferably better
Cripped Mode implemented and tested
Brian Melanson completes Oracle administrator training
DLT drives tested
Let's revise our timeline.
Am I right in believing that the following has occurred:
Alpha test proceeding.
The large cell test was postponed?
New tests were added for multi-tape checkpointing.
DLT testing
Stacker testing was added
System test plan and test suite have been delayed while we
code crippled mode.
How does this look for a revised schedule:
Code and unit test Crippled Mode 7/15 - 7/31
Write test plan and test suite 8/1 - 8/15
tests include Crippled Mode and performance tests.
Write Admin guide 7/15 - 8/1
Write improved user interface 7/15 - 8/30
Perform multi-cell test with Dev and ABS cells. 7/15 - 7/31
Perform test in Athena cell 7/31 - 8/15
Write migration plan (wdc) 7/31 - 8/15
Bottom line: Beta on 1 September?
----
One thing I would like us to think about is the process we've been using for
code reviewing.
Clearly the reviews have helped vrt in his writing of Crippled Mode.
But clearly also, Miki has uncovered aspects of the design she has
questions about.
I like the direction Miki is taking our review. It is less formal and
less oriented to the code, but may enable us to produce a better product
with less effort than reading every line of code ourselves.
I'd like to agree upon some new review methodology and put it into
our timeline.
-wdc
