[2642] in Release_7.7_team
Re: Please strongly consider backing out the zephyr servers
daemon@ATHENA.MIT.EDU (Jonathan McIndoe Hunt)
Thu Mar 8 19:13:48 2001
Message-Id: <5.0.2.1.2.20010308185622.039a2798@hesiod>
Date: Thu, 08 Mar 2001 19:10:54 -0500
To: Bill Cattey <wdc@mit.edu>, jis@mit.edu, Greg Hudson <ghudson@mit.edu>
From: Jonathan McIndoe Hunt <jmhunt@MIT.EDU>
Cc: Garry Zacheiss <zacheiss@mit.edu>, azary@mit.edu,
Greg Hudson <ghudson@mit.edu>, John Hawkinson <jhawk@mit.edu>,
release-team@mit.edu, op@mit.edu, winzephyr-release@mit.edu
In-Reply-To: <EudMh7tz0001N_g2hN@mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Hi All,
I wanted to clarify the support and testing status of the WinZephyr client
from the Software Release perspective.
A release effort has been underway to produce the documentation and a
customized installer to distribute the current version of WinZephyr with IS
support since January. Our target for releasing support is some time in
March. This information was provided via an announcement that was cc'd to
infosys on Jan 31, 2001.
To me, this means that the WinZephyr client was in the final stretch of
beta testing the application and is about to begin testing the
installer. This is quite a bit further along than the alpha testing that
was going on in 1999.
Support for the WinZephyr client was scheduled for sometime in
March. Based on the need to fix the bug that has caused this problem, that
will probably happen a little later than planned.
Is there a way to record who is connecting to the server from a WinZephyr
client that is not doing the right thing such that we can send a directed
communication to them to upgrade when we release the fully supported version?
Thanks,
Jonathan
p.s. for those that are interested in the WinZephyr Release work, see the
release notebook at
http://web.mit.edu/swrt/winzephyr
