[3198] in Release_7.7_team
Re: What is our installer strategy to be?
daemon@ATHENA.MIT.EDU (Garry Zacheiss)
Tue Mar 26 23:17:03 2002
Message-Id: <200203270417.XAA29427@indian-burial-ground-pet-store.mit.edu>
To: Bill Cattey <wdc@MIT.EDU>
cc: release-team@MIT.EDU, owls@MIT.EDU
In-Reply-To: Your message of "26 Mar 2002 22:16:52 EST."
<1017199012.5247.251.camel@tokata.mit.edu>
Date: Tue, 26 Mar 2002 23:17:01 -0500
From: Garry Zacheiss <zacheiss@MIT.EDU>
>> What should we be doing?
We've lived with the current installer for quite some time now; what
it does to GX150s is unfortunate, but since we've been putting up with
it for almost a year, putting up with it a little longer is acceptable
in my mind.
I agree that putting effort into Etherboot isn't a good use of
effort; it's something we want to move away from in the medium term.
I'm also in favor of expediting deployment of the new floppy. I'd
prefer for us to wait for Andrew to return before declaring it in
production, but I think it would be a fine thing to tell hotline it's
available, ask them to use it, and report any problems to us. They
would still have the old installer to use as a fallback; in fact, the
two should be able to exist in parallel for as long as want them to.
Setting a goal of having hotline test the installer for the next 2-3
weeksn and targeting a production deployment no later and the end of
April seems reasonable to me.
>> P.S. Did I mention that I burned Andrew's floppy into a CD and used it
>> to successfully do installs?
Neat. This also worked with the old etherboot based installer, and I
would've been surprised had it not worked with the new one.
Garry
