[2] in release-74
[carla@Athena.MIT.EDU: Notes from 3/19 ACT meeting]
daemon@ATHENA.MIT.EDU (Ezra Peisach)
Wed Mar 25 10:12:36 1992
To: rel74-mtg@zeus.MIT.EDU
Date: Wed, 25 Mar 92 10:12:23 EST
From: Ezra Peisach <epeisach@Athena.MIT.EDU>
Yesterday the mailing list pointed at menel....
------- Forwarded Message
Received: by E40-PO.MIT.EDU (5.45/4.7) id AA12584; Tue, 24 Mar 92 16:45:42 EST
Received: from MICKEY-MOUSE.MIT.EDU by Athena.MIT.EDU with SMTP
id AA14643; Tue, 24 Mar 92 16:45:37 EST
From: carla@Athena.MIT.EDU
Received: by mickey-mouse.MIT.EDU (5.61/4.7) id AA02800; Tue, 24 Mar 92 16:45:34 -0500
Message-Id: <9203242145.AA02800@mickey-mouse.MIT.EDU>
To: release-74@Athena.MIT.EDU
Cc: carla@Athena.MIT.EDU
Subject: Notes from 3/19 ACT meeting
Date: Tue, 24 Mar 92 16:45:31 EST
Hi! Here are the notes from last week's ACT meeting. Most of the
discussion dealt with the items on the ART list that had been in
Chris's bin, which is not included here. Each item was assigned to a
group.
In attendance: Mark, Peter, Tim, Lucien, Kevin, Chris, DOt, Carla, Ron
Hoffmann
Administrivia:
- - we'll create a public mailing list and discuss meeting [the list now
exists, but isn't public yet]
- - This meeting time is good. We'll meet as needed, probably not every
week
- - The people here are representatives of their groups, and should
communicate back to their groups. Being given responsibility for an
item doesn't mean that you have to do it yourself.
*Action item* Peter volunteered to request the definitive list of
items (with numbers down the side) from the Director of ACS
Other tasks:
- - user release notes -- Kevin
- - system release notes -- SysDev (LaTeX? Kevin will get back to them
if that would cause problems)
- - new stock answers and revise current ones -- Carla
- - need to identify user-visible vs. non-visible changes
- - revise other documents
- - testing
*Action item* -- cogent 1-page statement on most investigations (not
MH, x11r5 or AIX3.2) to ART by next Friday. (For ART it use to decide
whether or not it's a requirement)
*Action item* -- Mark will send proposed agenda for a week from Tuesday
to ART
*Action item* -- Sysdev will publish guidelines for submitting code
*Action item* (future) -- Sysdev will publish all changes made since
7.3
Kevin is afraid that some things will fall through the cracks and he
won't get to give input. He'll review the list and let us know which
particular items he's concerned about.
Preliminary schedule:
May 1 - code cut (but they'd like to see code before then)
May - build and friendly test
June - staff test
6/29 - release to Systems Support for copying
7/6 - to the field
A few pieces of the Sun port that have no impact on other platforms
are getting integrated into the source tree now, but that is not
guaranteed to continue.
Are man pages a release issue? The developer should submit a new man
page; TPS can provide someone to review them, and can submit fixed man
pages from this release. (The information for developers will be in
the guidelines)
CSS- What's going on with APT? Peter need to hand this off to them.
*Action item* -- Carla will check
================================================================
------- End of Forwarded Message
