From xemacs-m  Wed Jan 22 17:43:30 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 RAA11636 for <xemacs-beta@xemacs.org>; Wed, 22 Jan 1997 17:43:28 -0600 (CST)
Received: by crystal.WonderWorks.COM 
	id QQbzqs17266; Wed, 22 Jan 1997 18:43:27 -0500 (EST)
Date: Wed, 22 Jan 1997 18:43:27 -0500 (EST)
Message-Id: <QQbzqs17266.199701222343@crystal.WonderWorks.COM>
From: Kyle Jones <kyle_jones@wonderworks.com>
To: xemacs-beta@xemacs.org
Subject: Re: 20.0 release schedule
In-Reply-To: <m2wwt5uxad.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>
	<QQbzqo16320.199701222234@crystal.WonderWorks.COM>
	<m2wwt5uxad.fsf@altair.xemacs.org>

Steven L. Baur writes:
 > Kyle Jones writes:
 > > I'm talking about source code releases, not the full rock-n-roll
 > > releases with all the binaries.
 > 
 > We could do that.  Source code releases are relatively easy.  How
 > often do you wish to have the early 20.x releases?

To use VM as an example, the unplanned releases are bug driven.
Minor bugs can wait until the next normal release, which is when
I think modification have reached a critical mass.  Moderate
severity bugs get a fix within two days.  Showstopper bugs get a
release within hours of my reading the bug report.

Translating that in XEmacs-speak, given the size and complexity
of XEmacs, I'd expect moderate level bugs to be addressed in a
release three weeks after the first rollout, assuming that the
bugs are actually fixed by then.  If the bugs aren't fixed then
an interim release is, obviously, pointless.  And The point of
the release shoudl be increasing stability, no new features, no
matter how tempting.

