[2105] in Release_7.7_team
Re: Linux-Athena issue status
daemon@ATHENA.MIT.EDU (Jonathon Weiss)
Mon Feb 7 20:08:32 2000
Message-Id: <200002080108.UAA00632@stratton-forty-eight.mit.edu>
From: Jonathon Weiss <jweiss@MIT.EDU>
To: Greg Hudson <ghudson@MIT.EDU>
cc: release-team@MIT.EDU
In-reply-to: Your message of "Mon, 07 Feb 2000 17:16:27 EST."
<200002072216.RAA01668@egyptian-gods.mit.edu>
Date: Mon, 07 Feb 2000 20:08:25 EST
> To fix this, we need to modify athena-ws.rc and rebuild the
> athena-ws package. Right now athena-ws.rc only lives in
> Thomas's local working directory on kempis (a machine which
> I have remote access to, but not root access). I can
Sorry for the delayed reply, I had to re-read this in Garry's mail
before it sank in, and then spent some time talkign to Bill about it.
My initial reaction was that having sources that weren't checked in,
was itself a showstopper. For the past few years we have been very
careful not to put hand-edited files on the packs except in extremely
rare circumstances. When we do put hand-edited files on the packs we
are careful to think through why it is necessary, and make sure to
document it in release-team. To my knowledge none of this has
happened in this case. Additionally, I have no idea how many other
files are similarly not checked in.
After talking to Bill, he convinced me that there is some political
capiltal to be gained by having the deploy occur on the current
schedule (ie tomorrow). I'm willing to downgrade my concern from
"showstopper" to "makes me nervous" under a couple of conditions. I
want to know how exactly what files are not checked into the source
tree (is it just this one, or are there 300 of them or is it somethign
in between? Assuming this is not a completely unreasonable number of
files, and that someoen can copy them onto some other disk, I'd be
willing to see the deploy happen, tho as I said I'd still be a little
nervous about it.
I suspect it will fall to tb or ghudson to make the above
determination and file copies.
Jonathon
