[104] in Release_7.7_team
Re: AIX 3.2.5
daemon@ATHENA.MIT.EDU (Dorothy Bowe)
Fri Jun 17 12:39:11 1994
To: "Richard Basch" <basch@MIT.EDU>
Cc: release-77@MIT.EDU
In-Reply-To:
Date: Fri, 17 Jun 94 12:38:50 EDT
From: Dorothy Bowe <dot@MIT.EDU>
Most of this probably just duplicates John's mail, but anyway...
> 1. What testing procedure should be used?
First I would like to install 3.2.5 on two or three machines here in E40
and do some amount of testing. Most importantly, I would like to make
sure that all of our third party apps still ata bare minimum start & exit
cleanly.
After the initial testing, we could request volunteers for a more
extensive testing period. Maybe we could also update a few selected public
machines as we do during "staff" test, even if they have to be done by
hand. (John, you folks could deal with 2-3 re-installs, right?)
> 2. How should the hand-off of AIX 3.2.5 be done?
I'm not sure exactly what you mean here. John also asked:
>> Will there be a campaign to inform the people in Private
>> offices? Is there a mailing list so clients can ask questions like,
>> "Will going to 3.2.5 mess up my Version X.X of FrameMaker?"
I'd say yes, and ACS is the likely group to co-ordinate such a campaign.
However, this would not happen until we determine what the consequences are,
if any, of updating to 3.2.5.
> 3. Should there be an active push to update all machines to AIX 3.2.5 or
> just new machines (and re-installs)? There is currently no update
> procedure, and the best we will have is an automatic network re-install
If a network re-install is avaiable and all signs say go from whatever
testing period, I'd say to update/re-install all the public machines and
allow any private workstation owners who want to update to do so. The
latter would have to be handled on a case-by-case basis. If, however,
it's approaching the middle of the fall semester, we might consider
waiting until January to update public machines.
./dot
