[471] in Release_7.7_team
bugs and issues; what is a release issue?
daemon@ATHENA.MIT.EDU (Carla Fermann)
Wed Apr 10 12:09:04 1996
To: dot@MIT.EDU, mbarker@MIT.EDU
Cc: carla@MIT.EDU, sol24@MIT.EDU, release-team@MIT.EDU
In-Reply-To: Your message of "Wed, 10 Apr 1996 11:13:13 EDT."
<9604101513.AA13572@pianoforte.MIT.EDU>
Date: Wed, 10 Apr 1996 12:08:55 EDT
From: Carla Fermann <carla@MIT.EDU>
Hi! Sure, putting the lists in the release locker is fine. Future
updates to them will be made in those copies. Heck, I'll even
put a link from my directory there.
Now, about this MH thing... If this isn't a release issue, what is? To
me, a user-visible change that will be on all platforms is exactly
what a release issue is. Plus, since the decision to add mime support
as part of release 8.0 was made at the release-team level, shouldn't
future discussions about it also take place there?
Speaking as a humble support person, if there are going to be changes
such that messages that used to be readable no longer are, that better
be very well understood and documented.
I don't just think it would be "a great contribution to the summer
release" for someone to document the things that Mike listed, I think
it is critical. It should not be the case that consultants (or FL's or
SIPB people, or -i help people, or whoever) end up figuring out and
solving these on a case-by-case basis.
Carla
