[27032] in Athena Bugs
Re: Firefox question [help.mit.edu #356721]
daemon@ATHENA.MIT.EDU (John Hawkinson)
Thu Jan 11 01:33:20 2007
Date: Thu, 11 Jan 2007 01:20:46 -0500
From: John Hawkinson <jhawk@mit.edu>
To: Robert Basch <rbasch@mit.edu>
Message-ID: <20070111062046.GE6457@multics.mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <BF75F9F2-B42C-4C31-BA4F-042F31130865@mit.edu>
X-Spam-Flag: NO
X-Spam-Score: 0.00
Cc: David Wyman via RT <acis-help@mit.edu>, suggest@mit.edu, alexp@mit.edu
Errors-To: bugs-bounces@mit.edu
[ moved to suggest; bugs in the bcc. ]
Robert Basch <rbasch@MIT.EDU> wrote on Wed, 10 Jan 2007
at 23:31:34 -0500 in <BF75F9F2-B42C-4C31-BA4F-042F31130865@mit.edu>:
> (Not that it will help with this problem, but we will be updating to
> 1.5.0.9 in the next patch release).
I wanted to get this in email, though I'd alluded to it over zephyr
a few times recently.
I think it's a big mistake to not to move to Firefox 2.0 over IAP.
As the Spring picks up speed, Firefox 1.5 will be increasingly dated
and users will ask, "Why is Athena using this Ancient browser
when I use Firefox 2.0 everywhere else?" Even now, that feels
like the case.
I understand part of this is because we're using Red Hat's package.
But would it be such a big stretch to move to using mozilla's binary
package for i686 instead? (Solaris builds are available as well, from
http://releases.mozilla.org/pub/mozilla.org/firefox/releases/2.0.0.1/contrib/solaris_pkgadd/)
I think the release team should strongly consider it. The browser is
one of the anchor applications for which timely updates matter, but
it's also big enough that running it from a locker is really
frustrating.
Thanks.
--jhawk
