[829] in Release_7.7_team
Minutes of the Jan 21 1997 meeting
daemon@ATHENA.MIT.EDU (Greg Hudson)
Tue Jan 21 13:47:42 1997
Date: Tue, 21 Jan 1997 13:47:34 -0500
From: Greg Hudson <ghudson@MIT.EDU>
To: release-team@MIT.EDU
Cc: tytso@MIT.EDU
Attending: ghudson tytso jweiss wdc kcunning othomas dot brlewis
cfields
Action items:
* jweiss will send mail today to release-announce about the
upcoming patch release on the SGI.
* Ted Ts'o will look at the best way to modify libkrb5 to read
an /etc/athena/srvtab file and convert it on the fly if no
/etc/krb5.keytab file exists. This should be done by early
March. Greg will take care of the release side of the
change.
* Greg will try to have system release notes for the 8.1
release ready by April 8.
Decision items:
* We're still go on the SGI patch release.
* The 8.1 release will update the rlogind and rshd servers to
Kerberos 5, to clear the way for a full-scale migration in
8.2. (Updating the servers now smoothes the path to
updating the clients a year later, since new servers will
talk to old clients but new clients won't talk to old
servers.) As mentioned above, we expect these servers to be
using /etc/athena/srvtab instead of /etc/krb5.keytab in 8.1
even when they're doing krb5 logins, so we don't plan to
document anything related to /etc/krb5.keytab.
* We have a tentative release schedule:
- Release: July 1
- Early: June 3
- Beta: May 6
- Alpha: April 8
- Crash+burn: early March
Since we're not updating IRIX for 8.1, crash+burn really
only applies to Solaris. The Solaris 2.5.1 update should be
done by early March.
New features should done before Beta, hopefully before
Alpha. We have three features we want in the release:
Kerberos 5 rshd and rlogind, syncconf, and the Solaris
installer cleanup.
(From conversation after the meeting:) In past releases
(not counting 8.0), we've wanted to have a draft of the user
release notes by Beta (sometimes slipping to Early).
Therefore, the system release notes should be ready by
Alpha.
Information items:
* Another SGI seems to have had a problem similar to the one
Mike had on his machine; however, this SGI was in the public
cluster and did not take an update first. So whatever the
problem is, it doesn't appear to be directly related to the
update.
* Bill has an SGI kernel patch which seems to make Applixware
work (it currently panics the machine) and prevents some
other crashes. It's on the level of a Solaris jumbo patch.
Bill wants to settle some issues with SGI before giving us a
green light to put it in the release. Greg can do some of
the integration work now (making sure we can take a kernel
patch given the way we distribute kernels), but Bill needs
to give a green light for a specific version of the patch by
March 1 if we're going to do a patch release during spring
break.
