[360] in Release_7.7_team

home help back first fref pref prev next nref lref last post

Re: release suggestion form

daemon@ATHENA.MIT.EDU (Carla Fermann)
Thu Sep 21 16:06:12 1995

To: brlewis@MIT.EDU
Cc: dryfoo@MIT.EDU, release-team@MIT.EDU
In-Reply-To: Your message of "Wed, 20 Sep 1995 15:32:20 EDT."
             <9509201932.AA07780@joy.MIT.EDU> 
Date: Thu, 21 Sep 1995 16:05:52 EDT
From: Carla Fermann <carla@MIT.EDU>


Hi!

Sorry I missed the meeting today.

I understand that the form was discussed some, but I wanted to add my
comments anyhow. 

I think we'd be better off having people leave the resource
requirements part blank unless they really know what the impact would
be. People who do have the information will need to go in and correct
all the wrong things anyhow, so why bother having people guess wildly?

For example, there are several bug fixes or feature requests for
things like moira and register that seem very simple to a layman, but
really are pretty complex. (For example, my oft-reported problem with
it changing po servers when you fully register someone who has a
techmail account.) I think we're better off just having that cost part
blank until someone who really understands it completes it than for
someone to think "oh, it must be about 2 minutes worth of work" and
have it even initially end up on some list as a 2 minute project. 

					Thanks,

						Carla

home help back first fref pref prev next nref lref last post