[921] in testers

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

Re: unlog/aklog

daemon@ATHENA.MIT.EDU (daemon@ATHENA.MIT.EDU)
Wed Jul 25 08:59:37 1990

Date: Wed, 25 Jul 90 08:59:10 -0400
To: John F Carr <jfc@MIT.EDU>
Cc: Richard Basch <probe@MIT.EDU>, testers@MIT.EDU
In-Reply-To: John F Carr's message of Wed, 25 Jul 90 02:07:12 -0400 (EDT),
From: Richard Basch <probe@MIT.EDU>


   Date: Wed, 25 Jul 90 02:07:12 -0400 (EDT)
   From: John F Carr <jfc@ATHENA.MIT.EDU>
   References: <9007241112.AA03471@CRONOS.MIT.EDU>

   That aklog is not stable is not an excuse.  Aklog should not be immune
   from code cut.  The current version should be on the workstation root. 
   If changes are made, the new version can be installed in the release at
   that time, if it is not too late in the release process.

I don't want to keep hearing this, when I know it is still changing.
Thus, the following letter.  (I will take ownership of the tone of this
message and the "decision" contained here, but keep in mind that I have
had discussions with others, and others also believe that it is not
ready for the workstation root at this time).

Project leader's answer: NO, it is not ready for the workstation root.

I don't want to argue the point anymore.  I think it will be stable by
7.2m, but not for 7.1.  Keep in mind the release time-table; the new
features were only being debugged yesterday.  It is not "release
quality" yet.  I haven't even installed it in /afs/athena/service/,
but will be doing so, once I think it is fully-tested and stable.

End of argument. (You have to get Peter Roden to overrule me now, and if
this happens, I will argue it back to make sure both views are heard...)

-Richard

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