From xemacs-m  Sun Jan  5 18:46:52 1997
Received: from steadfast.teradyne.com (steadfast.teradyne.com [131.101.1.200])
          by xemacs.cs.uiuc.edu (8.8.4/8.8.4) with ESMTP
	  id SAA17812 for <xemacs-beta@xemacs.org>; Sun, 5 Jan 1997 18:46:51 -0600 (CST)
Received: from kiki.icd.teradyne.com (kiki.icd.teradyne.com [131.101.1.30]) by steadfast.teradyne.com (8.7.1/8.7.1) with ESMTP id TAA06253 for <xemacs-beta@xemacs.org>; Sun, 5 Jan 1997 19:49:48 -0500 (EST)
Received: from spacely.icd.teradyne.com (spacely.icd.teradyne.com [131.101.10.9]) by kiki.icd.teradyne.com (8.7.1/8.7.1) with SMTP id TAA03796 for <xemacs-beta@xemacs.org>; Sun, 5 Jan 1997 19:44:20 -0500 (EST)
Received: from spacely by spacely.icd.teradyne.com (SMI-8.6/SMI-SVR4)
	id TAA11042; Sun, 5 Jan 1997 19:46:29 -0500
Message-Id: <199701060046.TAA11042@spacely.icd.teradyne.com>
X-Mailer: exmh version 2.0beta 12/23/96
To: xemacs-beta@xemacs.org
Subject: Re: release plan (was Re: XEmacs 20.0-b34 is released) 
In-reply-to: pez's message of Sun, 05 Jan 1997 18:38:06 -0500.
	     <199701052338.SAA17268@axis.daedalusww.com> 
reply-to: acs@acm.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 05 Jan 1997 19:46:28 -0500
From: Vinnie Shelton  <shelton@icd.teradyne.com>

Pez wrote:
>     David> 	If you released 19.15 next week say, and
>     David> 20.0 in early Feb. It seems that a 19.16 could
>     David> be done in mid-feb if needed, but hopefully it
>     David> won't be needed? :)
> 
> Maybe I'm missing something big... could someone please
> explain to me why we would ever need a 19.16? How long do
> we plan to support 19.x versions?
> 
> I would say to get 19.15 out the door, and make sure you
> make it clear that 20.0 is coming *soon* (and mean it).
> Then for any bugs reported, just fix them in 20.0.
> Release 20.0 as soon as it's ready (incliding addressing
> any bugs reported against 19.15).
> 
> I guess a 19.16 just doesn't make much sense to me.

This is the the way I see it, too.  I don't anticipate a new release.  My 
hope is that 19.15 will be rock-solid, but my guess is that a few patches 
might be necessary.  I was proposing putting these on the web site.  If 
fixes were necessary for major bugs dealing with the C source, perhaps new 
binaries would have to be built, but I for one would encourage us *not* to 
do this if at all possible so we could concentrate on shaking more bugs out 
of v20.

--vin

