[431] in Release_7.7_team

home help back first fref pref prev next nref lref last post

Minutes, 2/15/96 Meeting (E40-316, 10:30 am)

daemon@ATHENA.MIT.EDU (Mike Barker)
Thu Feb 15 17:49:49 1996

To: release-team@MIT.EDU
Date: Thu, 15 Feb 1996 17:49:41 EST
From: Mike Barker <mbarker@MIT.EDU>


Agenda Items:
    Look at the support needed for solaris 2.4 going to the field
    (see the release order http://web.mit.edu/mbarker/www/porting/release.html)
    Look at the support needed for IRIX 5.3 going to the field
    (see the release order http://web.mit.edu/mbarker/www/porting/release.html)
    Define what "ding-dong, the witch is dead" has to do with the
        release team (i.e. rs6k machines are going--what do we need to do?)
    Define what Intel Unix boxes have to do with the release team
        ACMG approved spending two man-months + couple of machines on
        preliminary analysis of feasibility, with formal go/no go report
    Donuts


Key items:

1.  The rough schedule for Sol 2.4 and IRIX 5.3 going through the
release order steps is:

	alpha--Feb/March
	beta --April, May, June
        release-- July/Aug

This is aggressive.  The only reason I can lay out this fast a
schedule is that Miki has been working on Solaris 2.4 in the back room
for a while, and has made the transition much easier than it might be.

The release order material is open to change!  in particular, the
section on major lockers probably needs some refinement now that we've
explained what we are trying to do better.

One of the main reasons for making explicit the release order (and the
soon to come testing document) is that the traditional Athena
developers cannot and should not try to do all the items listed
themselves.  However, all of these items are needed to make a
"complete" release, so we are letting people know early that the
requirements for them to do testing and so forth will be coming.

2.  In late March/early April, Carla and Dot think we should put
together an article for the Athena Insider explaining what beta
machines will be available for locker owners and others to start
building and/or testing their parts of the system.

3.  When feasible, we should start letting users know that the RS6K
machines are leaving.

4.  We don't see any direct action for the release team at present in
regard to the Intel Unix feasibility study--aside from making sure that
resources are NOT diverted from the Solaris 2.4 and IRIX 5.3 porting
efforts.

5.  We will not hold a meeting next week.


home help back first fref pref prev next nref lref last post