[3146] in Release_7.7_team
Re: Netscape 6
daemon@ATHENA.MIT.EDU (Mike Barker)
Mon Feb 18 09:05:35 2002
Message-Id: <5.0.2.1.2.20020218085744.02a2eec0@po11.mit.edu>
Date: Mon, 18 Feb 2002 09:07:33 -0500
To: Theresa M Regan <tregan@mit.edu>
From: Mike Barker <mbarker@MIT.EDU>
Cc: Bill Cattey <wdc@mit.edu>, rferrara@mit.edu, vkumar@mit.edu, azary@mit.edu,
longpd@mit.edu, release-team@mit.edu, discovery-council@mit.edu,
jmhunt@mit.edu, jis@mit.edu, mjv@mit.edu
In-Reply-To: <5.0.2.1.2.20020213220141.072addc8@po12.mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Hi, all.
I would like to add a slightly different dimension to your discussions of
Netscape 6. Specifically, I don't think AMPS/EMCC necessarily needs
to be part of the browser discussions, since we don't "put out" a browser.
However, we do need to have sufficient warning that a new browser is coming
out, as we need to test our products (Stellar, etc.) using the new browser.
We also may have some suggestions about plugins and default configuration
(e.g. Streaming Media and Compression Services may have some requests about
plugins).
Frankly, we have already had comments about Netscape 6.2 on Mac OS X, and
have done some modification to make things work there.
I suspect there are other groups who also would be interested in hearing
early about the change, getting an early testing copy, and otherwise being
prepared before the new browser hits the streets.
So, in your planning for how to work through new browser releases, could you
add a "integration" phase where those of us who provide services that depend
on browsers get a chance to see what needs to change?
It's both a communications thing (letting those of us who aren't on the
"inner circle" have visibility into what has been learned) and a planning
thing (giving us a period when testing and modifications can be done).
Thanks
Mike
At 10:21 PM 2/13/2002 -0500, Theresa M Regan wrote:
>Good Day,
>
>At this juncture, I hesitate trying to respond to the various threads on this topic. I am not confident that I will be able to summarize my thoughts adequately.
>
>I do wish to raise an important dimension of recommending and/or supporting "browsers" at MIT and that is web certificates and their behaviour within our ever growing secure websites. I am not trying to diminish the "file save" issue being raised; however, within the Windows and Macintosh spectrums, we have had to delay announcing support for a particular browser because of certificate generation issues.
>
>If I am understanding the e-mail exchanges, the "release-team" needs some clarification and direction, sooner than later. From my perspective, a browser discussion requires the following people...
>
> Bill Cattey -- representing the "release-team" (this covers athena and its various flavors, as well as, LinuxAthena)
> Jon Hunt/Ginny Williams -- Software Release Team
> Lee Ridgway -- Netscape Product Release Coordinator
> Jeff Schiller -- Certificate expert
> Marshall Vale -- Macintosh Development (in particular, MacOS X and certificate issues)
> Discovery Council
>
>Did I overlook any other key roles?
>
>For completeness, we do need to test IE web certificate acquisition under Windows if any changes are made to the certificate server to accommodate issuing certificates under Netscape 6
>
>Once we are confident of the participants, I will try to arrange a convenient meeting, as well as, work with Bill (and any other volunteer(s)) to summarize the discussion and issues.
>
>Thanks,
>Theresa
