[2725] in Release_7.7_team
Re: What's our Open AFS Validation plan?
daemon@ATHENA.MIT.EDU (andrew m. boardman)
Mon Apr 30 14:12:21 2001
Date: Mon, 30 Apr 2001 14:12:16 -0400
Message-Id: <200104301812.OAA09025@pothole.mit.edu>
From: "andrew m. boardman" <amb@MIT.EDU>
To: wdc@mit.edu
CC: release-team@mit.edu, ted@mit.edu
In-reply-to: <AuvN0jtz0001JZNu5o@mit.edu> (message from Bill Cattey on Mon, 30
Apr 2001 16:17:51 +0000 ())
>I think our "plan" up to now was for Garry to fetch the sources, build
>them and fiddle with them until they were in good enough shape to hand
>off to Andrew for beta deployment, and then we were going to cross our
>fingers.
As it turns out, I've been hacking on it as well since there's a fair
amount of grotty kernel module debugging under our miniroot that I need
to do to figure out why the install doesn't work. (There is a fairly
undesirable workaround for getting the install working (2.2.17 with a
transarc module) if it comes to it.) The 9.0.1 alpha machines are all
running OpenAFS, and will continue to do so barring really horrible
lossage, which (so far) hasn't happened.
Do we know much about the tests that Transarc was doing? Anything much
more sophisticated than "shovel lots of data over the network and see if
it gets there intact"? (Which is certainly better than the "release it
and wait for bug reports" plan...)
