[773] in Release_7.7_team
Agenda for 10/31
daemon@ATHENA.MIT.EDU (Mike Barker)
Wed Oct 30 14:47:17 1996
To: release-team@MIT.EDU
Date: Wed, 30 Oct 1996 14:45:49 EST
From: Mike Barker <mbarker@MIT.EDU>
Donuts, good talk, and perhaps we could go over my draft plan for SGI...
See you at 10:30, usual place.
mike
------- Forwarded Message
A Rough Draft Plan
To help us get started on planning the SGI effort for the next year or
so, here is a VERY rough plan. The triplex numbers are guesses at the
best, average, and worst-case times in person-days.
One issue: Are the time estimates (working days) reasonable? too
short? too long? You might try making your own first, then telling
me how far off I was.
Second issue: Are these most of the tasks, steps, things we have to do
to get there? What did I forget? Which ones are really stupid ideas?
Thanks
Mike
Goal: SGI 6.x Port (MAY NOT BE NEXT YEAR!)
Steps/Deliverables:
1. An installed SGI 6.2 system (straight sgi product) - 3, 5, 30
vrt- we need to obtain a large enough hard disk 2 + gb.
[Oct 21 - vrt was getting quotes on 4 gig disks]
2. List of plus/minus points (costs and benefits, risks, etc.) to changing
from SGI 5.3 to SGI 6.2 - should be initial draft, plus periodic updates
Initial Draft - 5, 10, 20
periodic updates - 2, 5, 20 per update
vrt- Initial draft will probably take longer
3. List of 3rd party software used/desired on Athena - annotated to show
availability under IRIX 6.2 - 5, 10, 20
vrt- One of the problems we will have to deal with is the fact most
vendors will just say to use the compatibility. Any vendor
that uses the irix4 compat stuff we will lose.
4. List of 5.3 to 6.2 changes - annotate to show plus, minus, or neutral
for MIT use - 5, 15, 30
vrt- Our changes or theirs.
[I was thinking of their changes, but we may also want to track what
we want to change in this migration]
5. List of modifications needed (a design, a refined porting list, etc.)
5, 10, 20 to make list + 2, 5, 10 for review and refinement of design
6. Each modification needs to have a design, review, code, review, test
cycle; plus documentation - especially
a. install - 5, 20, 40
b. update - 3, 5, 10
c. login/reactivate - 2, 10, 20
vrt- probably right. I think those will need fairly specific WBS.
7. Refined "porting list" - take the rough one used this year, modify to
provide more details, add test protocols and such where available
initial revision - 1, 5, 10
collect/create test protocols, shell scripts, etc. - 3/5/10 per month?
vrt- Probably more if we want to "Do this right"
8. Alpha, beta, early, and release - like this year, except we can estimate
times and effort needed better.
------- End of Forwarded Message
