[369] in Release_7.7_team
Meeting Notes 11/2
daemon@ATHENA.MIT.EDU (Mike Barker)
Tue Nov 7 14:58:23 1995
From: Mike Barker <mbarker@MIT.EDU>
To: release-team@MIT.EDU
Cc: mbarker@MIT.EDU, wdc@MIT.EDU
Date: Tue, 07 Nov 1995 14:58:23 EST
The Athena Release Team (ART), like other parts of IS, has an
opportunity to redesign the process of doing our work.
The challenge before us is for ART to make decisions about the
upcoming release, with appropriate negotiation and commitment of
resources from the various parts of IS.
Where necessary, ART will also have to escalate decisions, pointing to
the effects on the release of changes, backpedaling, and other common
actions.
Part of turning ART from a group that has a "coordination meeting"
into an "effective action" team is the conscious decision to have
members of ART:
o report release plans and needs to their departments
o make binding commitments for their departments to perform release
efforts
We expect that the membership in ART may change as rest of IS moves to
teams and the working methods of ART are delineated.
We see four major directions for ART:
1. information dissemination (the current role)
2. definition of release policy
3. schedules
4. collection and management of commitments to schedules
In the near future, we expect to work on the following:
1. ART Charter
2. "Whatsa release"
3. Schedule
4. Team membership
5. Commitments from all affected teams and processes
6. Publicize the new role of ART
While we are doing this, we also expect to work towards the next release.
Thursday's Agenda
1. ART Charter
2. Whatsa release
and, as usual, donuts (save those holes for dot)
Draft Charter
The Athena Release Team plans, coordinates, and reviews all work
required to provide consistent and effective Athena software releases
to the MIT academic community.
Mike
