From xemacs-m  Wed Jan 22 16:34:17 1997
Received: from crystal.WonderWorks.COM (crystal.WonderWorks.com [192.203.206.1])
          by xemacs.org (8.8.4/8.8.4) with ESMTP
	  id QAA11150 for <xemacs-beta@xemacs.org>; Wed, 22 Jan 1997 16:34:15 -0600 (CST)
Received: by crystal.WonderWorks.COM 
	id QQbzqo16320; Wed, 22 Jan 1997 17:34:14 -0500 (EST)
Date: Wed, 22 Jan 1997 17:34:14 -0500 (EST)
Message-Id: <QQbzqo16320.199701222234@crystal.WonderWorks.COM>
From: Kyle Jones <kyle_jones@wonderworks.com>
To: xemacs-beta@xemacs.org
Subject: Re: 20.0 release schedule
In-Reply-To: <m2k9p57gee.fsf@altair.xemacs.org>
References: <m2k9p7jo6f.fsf@altair.xemacs.org>
	<u94tg922e0.fsf@neal.ctd.comsat.com>
	<QQbzpp11213.199701221620@crystal.WonderWorks.COM>
	<m2k9p57gee.fsf@altair.xemacs.org>

Steven L. Baur writes:
 > I'm not sure it's feasible to get releases more frequent than two
 > months apart, but I do not intend to let any of the early 20.x's sit
 > for very long until we get more code tested and stabilized.  If we get
 > up to 20.6 by year-end, so be it.

What is the sticking point?  Why is doing a release so hard?  I'm
talking about source code releases, not the full rock-n-roll
releases with all the binaries.

