[1981] in testers
Re: xtechinfo
daemon@ATHENA.MIT.EDU (lwvanels@Athena.MIT.EDU)
Mon Jun 1 14:05:47 1992
From: lwvanels@Athena.MIT.EDU
Date: Mon, 1 Jun 92 14:05:24 -0400
To: kcunning@Athena.MIT.EDU
Cc: testers@Athena.MIT.EDU, cavan@Athena.MIT.EDU
In-Reply-To: [1979]
Reply-To: lwvanels@MIT.EDU
Code freeze is for source used to build the srvd's; the actual binary for
xtechinfo will be in a locker, and can be changed outside of the release.
The only part of xtechinfo in the release is the shell script that attaches
the correct locker and runs it from there. This shell script may not get as
much testing as it might since the actual xtechinfo binary doesn't exist,
but it is fairly simple. The testing of the xtechinfo binary will take
place once it is available, which is in a different timeframe than the current
release. However, since any problems which show up can be fixed outside of
the release, this doesn't mean that potentially buggy program will be frozen
in place.
I'm not the person in charge of the xtechinfo project, so I can't tell you
what sort of contingency plans they have in case it turns out to be really
late, but since the current behavior is to fall back to the ascii version, I
don't see any serious problems with leaving the link there even if xtechinfo
isn't available shortly.
-Lucien
