Subject: I think this went by a coupla weeks ago....

From: Dave Remien <[email-masked]>
Date: Tue, 22 Mar 1994 08:13:58 -0600 (MDT)

Howdy!

If my memory is working (not a likely thing), a discussion of the 
Reply-To: field went by a couple of weeks ago. Was the end result that 
Reply-To: would be in Pine 3.90?

TIA,

Dave

---

From: David L Miller <[email-masked]>
Date: Tue, 22 Mar 1994 08:55:45 -0800 (PST)

Yes.

|\ |  |\/|  David L. Miller    [email-masked]  (206) 685-6240
|/ |_ |  |  Software Engineer, Pine Development Team   (206) 685-4045 (FAX)
University of Washington, Networks & Distributed Computing, JE-20
4545 15th Ave NE, Seattle WA 98105, USA

---

From: Terry Gray <[email-masked]>
Date: Tue, 22 Mar 1994 09:02:36 -0800 (PST)

Yes.

-teg

---

From: "Robert A. Hayden" <[email-masked]>
Date: Tue, 22 Mar 1994 14:47:34 -0600 (CST)

As long as we're talking about things for the 'next version':

Any chance the ability to automatically BCC to distributions instead of 
having to mess with the full headers and all that can be added/considered?

*ducks*

____        Robert A. Hayden          <=> [email-masked]
\  /__          -=-=-=-=-             <=>          -=-=-=-=-
 \/  /   Finger for Geek Code Info    <=> Political Correctness is
   \/  Finger for PGP 2.3a Public Key <=> P.C. for "Thought Police"
-=-=-=-=-=-=-=-
(GEEK CODE 1.0.1)  GAT d- -p+(---) c++(++++) l++ u++ e+/* m++(*)@ s-/++
		       n-(---) h+(*) f+ g+ w++ t++ r++ y+(*)

---

From: Ed Greshko <[email-masked]>
Date: Wed, 23 Mar 1994 08:03:09 +0800 (TPE)

> As long as we're talking about things for the 'next version':

	When will 3.90 be out.  I've heard it is in beta test at the
moment.

Edward M. Greshko			Control Data Taiwan
Voice: +886-2-715-2222 x287		6/F, 131 Nanking East Road, Section 3
FAX  : +886-2-712-9197			Taipei, Taiwan R.O.C

---

From: Terry Gray <[email-masked]>
Date: Tue, 22 Mar 1994 18:27:06 -0800 (PST)

On Wed, 23 Mar 1994, Ed Greshko wrote:

> 	When will 3.90 be out.  

Ed, We've given up answering that question for Lent :)

> I've heard it is in beta test at the moment.

Gosh... we didn't know that!

Email from Pine team members will typically say 3.90 in the MsgID since 
we do try to inflict new code on ourselves before others, but so far the
3.90 development code has only been used by us, and development is 
continuing.  

We were just talking about schedules this morning, and didn't reach a 
conclusion, except that it was definitely past next Tuesday :)

Since there is still have more stuff we want to get in, I'm guessing 
a Beta release in May or thereabouts.  But that's a guess, and Mike 
hasn't heard me say it before now...

-teg

---

From: Barry Landy <[email-masked]>
Date: Wed, 23 Mar 1994 15:32:46 GMT

> hasn't heard me say it before now...

"Early Spring" (a previous estimate) is clearly late this year :-)

-------------------------------------------------------------------------------
Barry Landy                        Computer Laboratory:+44 223 334600
Head of Systems and Development    Direct line:        +44 223 334713
University of Cambridge Computing Service
New Museums Site                   Email:[email-masked]
Pembroke Street, Cambridge CB2 3QG

---

From: Terry Gray <[email-masked]>
Date: Wed, 23 Mar 1994 08:59:24 -0800 (PST)

> "Early Spring" (a previous estimate) is clearly late this year :-)

See, I *knew* I should never answer any question concerning dates! :)

Clearly, we are better at design and coding than prediction; however, let
me take this opportunity to jump further into the deep end... 

 o First, I'll observe that May is still Spring in Seattle, and indeed
   up thru May 5th or so, perhaps even *early* Spring :) 

 o Second, we are planning to use the term "Beta" for this upcoming
   release as a matter of Truth in Advertising and as an attempt to
   properly set expectations.  It doesn't necessarily mean the code
   will be any worse than usual :), but we want to be clear that it
   will have a bunch of new features, and a corresponding number of 
   new bugs to complement the bugs that are fixed in it.

 o Since Pine has now been ported to a lot more platforms than we use
   internally, we have discovered the concept of "platform-specific bugs".
   We want to be conservative in how the release is advertised, and 
   that suggests that folks with different environments should have a
   chance to find some of those platform-specific bugs before the general 
   populace assumes that a higher version number is in all respects
   superior to a lower one :)

 o Schedules are vaguely related to feature sets.  We try to avoid 
   committing to specific feature sets in releases (or schedules, for that
   matter!) so that if our internal estimates should ever prove overly
   optimistic (what??) we can "readjust" the goal without having to eat
   too much crow.  In this case, there are still a few things we know you
   are all waiting for that aren't done yet, so --alas-- it won't be
   March, especially with IETF next week.  Beyond that, we'll see.  We
   have some local requirements that will prevent us from delaying this
   blessed event *too* much longer...

So in short: "late this year" is probably when some very conservative
folks will adopt this code, or its successor, but by then we certainly
intend to have another new version with additional features to confuse the
issue.  On the other hand, *some* places will probably be running 3.90 in
production before Spring is over.  (Hey, *I'm* using it in production
already... but then it did crash once yesterday :)

-teg