[140] in Release_7.7_team
Meeting on Friday, July 29
daemon@ATHENA.MIT.EDU (Dorothy Bowe)
Thu Jul 28 10:30:15 1994
To: release-77@MIT.EDU
Date: Thu, 28 Jul 1994 10:29:44 EDT
From: Dorothy Bowe <dot@MIT.EDU>
Yes, we have another meeting scheduled for this Friday, July 29 at 10:30
in the small conference room. (That's tomorrow.) The main purpose for
this meeting is to make sure we're ready for field release next week,
but as time permits I'd like to begin addressing the question of "What
next?".
Agenda
------
1. Status Check
a. Packs (release engineering)
i. current versions
ii. planned releases
b. Open Problems (dot, rel eng)
c. Release Notes (kevin)
d. Posters (kevin, dcns-cluster)
e. Disk Space for System Packs (dot)
f. Public workstations (dcns-cluster)
g. Consultants (carla)
h. Notifying RCCs (?)
i. Courseware (dot)
2. Where do we go from here?
(Obviously), the "first next" step from here is to actually get a
release out to the field, but what happens after that? Traditionally,
releases have hit the field, and after a minor patch or two to fix major
problems, the release is over and the release team disbands. The
first question I would like to consider on Friday is something like
this:
Are we, as a team, happy with the release as it is? confident in
its stability? If yes, what is our reasoning? If no, what do we
want to do about it?
The second and final item I want to begin to consider under "Where do we
go from here?" is something of a post-mortem on the release 7.7 process.
("But it's not even over yet!") My guess is that if we had to do it all
over again, there are some things we'd leave unchanged, others we'd do
differently and still others that don't work at all. (Remind me not to
get too smart with AFS system packs and links!) At some point after the
release hits the field it would be really nice to gather our thoughts so
that the next release (assuming that there is one) can benefit from our
experience. It's not something we really have to do, and I don't want
to get into "re-engineering" the release process, but it could be a very
useful exercise. In any case, I don't expect to deal with this on
Friday, but rather discuss a time to consider it.
Thanks as always and see you tomorrow,
./dot
