[210] in Release_7.7_team
Re: Meeting minutes 11/17/94
daemon@ATHENA.MIT.EDU (Dorothy Bowe)
Sun Nov 20 14:45:48 1994
To: ghudson@MIT.EDU
Cc: mhbraun@MIT.EDU, release-77-mtg@menelaus.local
In-Reply-To:
Date: Sun, 20 Nov 1994 14:45:40 EST
From: Dorothy Bowe <dot@MIT.EDU>
>
> > [For those of you who don't like to read long minutes, #3 summarizes
> > the release team's recommendations for the summer release. If you
> > have any interest in expressing your opinion on these
> > recommendations, please speak up now.]
>
> Yeah. If I remember correctly, better Zephyr authentication was
> listed as a 5 for importance and a 4 for likelihood, but it's not
> listed anywhere in the minutes.
>
Yes, and "secure zephyr" is still on the list to be included in the
release this January. The items discussed at the last release team
meeting were strictly for the release next summer and that's why zephyr
changes were not included. (If you're interested in the status of any
item which was suggested for inclusion in any release, check out
/mit/release77/Release7.8/Suggestions.)
> The code has been written, integrated into the zephyr locker, and a
> week ago I sent out a call for testers with fairly wide distribution.
> After a couple of build-related problems were corrected in the first
> day of testing, no one reported any problems with the new clients, and
> a few people have reported that everything works fine.
>
> Bringing this into the release should be simply a matter of taking a
> snapshot of the zephyr locker (and doing the usual modifications to
> the configuration) before the code cut.
>
Code cut is set for December 1. As long as the code is in to release
engineering by then, we should have it out to the field at the end of
January.
> Also, perl 5 is advertised as providing a very high level of
> backward-compatibility. It is probably worth testing on a few
> non-trivial scripts to see if anything breaks. Waiting until the fall
> release wouldn't be such a bad idea, though.
>
I agree.
Dot
