[2088] in Release_7.7_team

home help back first fref pref prev next nref lref last post

Linux deploy

daemon@ATHENA.MIT.EDU (Thomas Bushnell, BSG)
Sat Feb 5 01:51:14 2000

To: Bill Cattey <wdc@MIT.EDU>
Cc: release-team@MIT.EDU, zacheiss@MIT.EDU, joewelch@MIT.EDU
From: tb@MIT.EDU (Thomas Bushnell, BSG)
Date: 05 Feb 2000 01:51:05 -0500
In-Reply-To: Bill Cattey's message of "Thu,  3 Feb 2000 16:24:57 -0500 (EST)"
Message-ID: <u1h9010f8h2.fsf@mary-kay-commandos.mit.edu>


Here is the current status.  I'm about to build the complete packages
for the release, which will get called 8.3.25.  (For the duration of
8.3 there will probably not be close synchronization of patch release
numbers though; I'm not sure exactly what Greg plans.)

The current code is not bugfree but it is what we have been using
layered for a while now with some additional bugfixes.  A fair bit of
bugfixing work does still remain, but I am confident that we won't
lose making this release.

I am not able to meet with Joe to hand him the floppy.  The
instructions are /mit/bootkit/rhlinux/INSTRUCTIONS and the floppy
image is /mit/bootkit/rhlinux/3c90x.fl.  I have also handed Garry
Zacheiss a boot floppy.

I have my doubts about whether the update will work in these packages;
Greg has a lab-tested update script, but the reactivate process might
not fully work with it, especially since we haven't tested it at all.

My proposal then is as follows:

* Proceed and install the workstations on Tuesday.

* Wait a few days to let things chill.

* I have some medium-importance changes that need to get made; I'll
  coordinate with Greg to try an update of such changes and we can see
  whether it works or not.  I'd like to do that Friday.

* If the update works, then the other fixes that we will be making in
  the near term can be released.  I'd like it if we can have a more
  rapid release-timing procedure for at least a month or so; ideally I
  think Greg and I can prepare the release, test it, and ask for ops
  to propogate it to the athena call all within a few hours (unless
  staff time or disk space forces a delay, of course).

* If the update fails, then we'll have to update by hand until we have
  a working version and for the first few cycles of bugfixes.  I'll
  take the responsibility for dealing to make this happen myself.

Thomas

home help back first fref pref prev next nref lref last post