[48] in Release_7.7_team
Meeting on April 8
daemon@ATHENA.MIT.EDU (Dorothy Bowe)
Fri Apr 1 10:21:56 1994
To: release-77@MIT.EDU
Date: Fri, 01 Apr 94 10:21:26 EST
From: Dorothy Bowe <dot@MIT.EDU>
We have a meeting scheduled for 11 AM on Friday, April 8th, in the small
conference room. (That's next week.) The main purpose of this meeting
is to check the status of development and catch any potential problems.
(Not that I expect any :-) ) However, since we're going through the
trouble of having a meeting, I thought I'd throw a second item on the
agenda, and that is to brainstorm about testing.
As we pointed out many times when talking about the proposed items,
testing tends to be one of our major problems in putting together a
release. I don't think we're going to solve the problem, but we can at
least try to do something. My idea is to go through the release item
list and see if we can identify at least one these three things for
each:
* A list of things which we know must get tested. An example of
this would be emacs, where we had sure better test saving
files when over quota.
* A person or persons who needs to do testing or review. An
example of this might be NEOS, where we need to have someone
like Ed Barrett in on the testing. Another example might be
dm/xlogin fix, where we need to have the code audited.
* A person or persons to be assigned to testing. (I don't think
we have to name this person yet, just note that someone has to
be there.) The best example for this would be AIX where we
have to make sure *someone* sits down and uses the system
during testing.
And that all makes the agenda:
Release 7.7 Meeting #6
----------------------
1. Status check
- who's working on what, and what problems can we identify
2. Testing brainstorm
3. Next meeting
./dot
