From xemacs-m  Sat Jan  4 20:42:24 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 UAA09430 for <xemacs-beta@xemacs.org>; Sat, 4 Jan 1997 20:42:24 -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 VAA14996; Sat, 4 Jan 1997 21:45:17 -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 VAA28193; Sat, 4 Jan 1997 21:39:50 -0500 (EST)
Received: from spacely by spacely.icd.teradyne.com (SMI-8.6/SMI-SVR4)
	id VAA07008; Sat, 4 Jan 1997 21:41:57 -0500
Message-Id: <199701050241.VAA07008@spacely.icd.teradyne.com>
X-Mailer: exmh version 2.0beta 12/23/96
To: Steven L Baur <steve@miranova.com>
cc: xemacs-beta@xemacs.org
Subject: Re: XEmacs 20.0-b34 is released 
In-reply-to: steve's message of 04 Jan 1997 18:24:46 -0800.
	     <m2hgkw505t.fsf@altair.xemacs.org> 
reply-to: acs@acm.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 04 Jan 1997 21:41:57 -0500
From: Vinnie Shelton  <shelton@icd.teradyne.com>


steve@miranova.com said:
> It has been suggested by Martin that 20.0 be released with 19.15 and I
> agree.  I like 20.0 a lot.  Let's see if we can get them both out in a
> couple weeks. 

This seems like a very bad idea to me.  If you dislike maintaining 2 source 
trees, you'll really hate tracking down bugs in 2 different versions.  
Here's my suggestion:

1) Release 19.15 very soon.  I think your current schedule looks good.  The 
release is very stable.  I think pre-release1 will probably be of release 
caliber.

2) Fix all the bugs that users report.  Remember I offered to maintain an
officially sanctioned patch list, and perhaps get some updated binaries to 
the ftp sites.

3) This should give you time to:
  a) make sure that all the fixes/enhancements/improvements in 19.15 have 
made it to 20.0
  b) complete the performance work which is probably necessary for 20.0.

In general, the idea of making 2 simultaneous releases is bad because it 
will confuse users and dilute our resources.

If you really want to release 20.0 now, then you should not release 19.15, 
but I think this would be a bad idea.

My $.02.

--vin

