MEMORANDUM

TO:	Rick Greenblatt
FROM:	Keith Corbett
DATE:	27-Jun-88
SUBJ:	Status report
COPY:	Jim O'Dell, Guy Chevalier

The group's activity over the past few weeks has focused on two areas:
1) the impending major system release of Lambda software (Release 4), and
2) various K-machine internals documentation efforts.  This is in
keeping with our priorities, as discussed below:

        1) Release
        2) Maintenance
        3) Integration and Quality
        4) Documentatation and support

1. Priorities

For the past several weeks Peter and I have been working together on
release 4.  David and I, working with Bob and Jim, have concentrated on
the K-Machine/Macintosh interface document.

2. Design / Documentation

The K/Mac interface document is both a functional specification and
design issue outline.  The meetings held this month, both in Cambridge
and Montreal, have been very productive.  Many complex issues need to be
further ironed out, but it has become clear that

  1) Cambridge has made substantial progress on specifying requirements
and design parameters, and

  2) Our group will have a lot of work to do on integrating the code
into the LISPM system software.  [We cannot proceed on integration at
this time because a) Montreal has to catch up on design clarifications
made recently, and b) we need further meetings.]

Our major ongoing need is more direct interaction between the two
groups.  I have three suggestions for improving communication and
productivity.  All of these methods may, in the end, be required.

   1) A real-time, on-line TCP file transfer mechanism between the two
groups.  Serial-IP, my extension to Lambda networking, requires 3-4
more days of my time to get it working for modem connections.

   2) The Montreal group expressed an interest in having one of us (I
volunteered) come up for an extended stay, perhaps one week.  This would
be appropriate just after they resume work, with a bus coupler.  I could
help them with LISP problems that have arisen, and get ready for later
integration efforts.

   3) When they have a prototype that works with the bus coupler, they
should send somebody down here for 1 week, who will help us with the
integration and answer questions about their implementation.  This will
augment any implementation documentation they are able to provide
up-front.

3. Software Validation

I have ported the ISI CommonLISP code validation software and various
CommonLISP test suites.  It is truly interesting to see what people think
of as "vanilla" CommonLISP.  But, overall, the test suite has made an
important contribution to our endless quest toward perfection.
I have also begun a ZetaLISP test file, for standard ZL features that we
need to verify from time to time.  So, the suite is an ongoing,
expanding concern.  The tests must be run periodically, for example after we
cut a new cold load (by the end of this week).  It could alert us
to new problems that get introduced with system updates.
                                    
4. Release 4

The group has made numerous fixes to various system components, including
1) low-level utilities such as the compiler, 2) ZMail (the editor), 3)
CommonLISP compatibility, and 4) the network/file-system.  Many of the
fixes were motivated and facilitated by the (newly fixed) bug database
and (newly ported and fixed) LISP validation/testing system.

The last "Top Priority" bug fix was made yesterday, and the code is, if
not "frozen", then cooled down.  We will begin recompiling the system
today, followed by a cold load (2 days work).  Then we will double-check
the software (simply running it for 3-5 days).  If all goes well, we
will be able to make master tapes by the middle of next week.

I have discussed the final phase of release activities with Clovis Regis
and Guy Chevalier.  Both Manufacturing and Admin.  will be needed to
handle production and distribution.

5. Internal Support

Peter and I both some time (almost daily) assisting the more junior
staff with various programming and utility problems on the Lambda.  This
is a worthwhile aspect of our group's role; aside from normal
engineering development and maintenance, we provide internal support,
integration, and general system software advice.  Happily, with the
recent additions of Steve and Bob, there are more senior programmers to
go around.

A typical example of internal support is some time that I (in addition
to others) have put into setting people up for electronic mail.  This
includes maintaining the text file record (bugs history) and bug
database.  The latter is one of the most important tools, and it was
very badly broken when we began work on it last month.  It is now almost
straight-forward, and is much more useful.

6. Resources and Problems

My own efficiency has been somewhat hampered recently by the fact that
David and I share one fairly undependable 2x2.  I need another
workstation, and the 2x2 we share has been down for a total of 5 days in
4 weeks.  At this moment I am waiting for a memory board from Lowell.  I
have discussed with Henry and Clovis the possibility of bringing one of
my systems down from Lowell, which would be a great improvement.