From xemacs-m  Tue Dec 10 10:57:15 1996
Received: from altair.xemacs.org (steve@xemacs.miranova.com [206.190.83.19]) by xemacs.cs.uiuc.edu (8.8.3/8.8.3) with ESMTP id KAA24584 for <xemacs-beta@xemacs.org>; Tue, 10 Dec 1996 10:57:14 -0600 (CST)
Received: (from steve@localhost)
          by altair.xemacs.org (8.8.4/8.8.4)
	  id JAA18962; Tue, 10 Dec 1996 09:07:12 -0800
Sender: steve@xemacs.org
To: xemacs-beta@xemacs.org
Subject: XEmacs release schedule (was Re: XEmacs 19.15-b3 is released)
References: <m2wwurot6v.fsf@altair.xemacs.org> 	<y9lafrmkfs6.fsf@modas.informatik.uni-tuebingen.de> 	<199612100802.AAA21562@xemacs.eng.sun.com> <199612101553.KAA03450@anthem.CNRI.Reston.Va.US>
X-Url: http://www.miranova.com/%7Esteve/
Mail-Copies-To: never
X-Face: #!T9!#9s-3o8)*uHlX{Ug[xW7E7Wr!*L46-OxqMu\xz23v|R9q}lH?cRS{rCNe^'[`^sr5"
 f8*@r4ipO6Jl!:Ccq<xoV[Qz2u8<8-+Vwf2gzJ44lf_/y9OaQ`@#Q65{U4/TC)i2`~/M&QI$X>p:9I
 OSS'2{-)-4wBnVeg0S\O4Al@)uC[pD|+
X-Attribution: sb
From: Steven L Baur <steve@miranova.com>
In-Reply-To: "Barry A. Warsaw"'s message of Tue, 10 Dec 1996 10:53:41 -0500
Mime-Version: 1.0 (generated by tm-edit 7.95)
Content-Type: text/plain; charset=US-ASCII
Date: 10 Dec 1996 09:07:11 -0800
Message-ID: <m2iv6as4zk.fsf_-_@altair.xemacs.org>
Lines: 58
X-Mailer: Red Gnus v0.72/XEmacs 20.0

>>>>> "BAW" == Barry A Warsaw <bwarsaw@CNRI.Reston.VA.US> writes:
>>>>> "MB" == Martin Buchholz <mrb@eng.sun.com> writes:

MB> I vote for having the package owners themselves decide when a
MB> release is solid enough to include in public distributions.
MB> This should apply to gnus, cc-mode, w3, etc...

That is my vote as well.

MB> It's real important for the maintainer to ping various package
MB> owners sometime before a release and do package upgrades, so
MB> they can be tested before the release goes out.

BAW> It would be great if you could just post a release schedule, even
BAW> if it ends up slipping a bit.  Include code freeze milestones,
BAW> etc., so we can know when we've got to have things ready for you.

I *really* want to make something available for xmas eve (`XEmacs for
xmas').  And I desperately want to get rid of two working source
trees.

XEmacs 19.15 is frozen except for critical bug fixes and performance
improvements.  XEmacs 20.0 is slightly less frozen, and I want to get
certain improvements like frame in a glyph, and the packaging patches
in when convenient (1Q97).

BAW> I know I have a few patches to some of my stuff, but since my
BAW> free time is so limited, I usually will wait until the last
BAW> minute to nail down the loose ends and send them out.

Priorities for the next month:
1. Performance
2. Bug Fixes

As soon as I get 20.0-beta31 out, I'd like to spend a week where we're
doing nothing but running performance benchmarks.

Tentative release schedule:
24-December:
Source release 19.15, 20.0 (binaries to follow on 19.15 as folks get
back from vacation).

15-January:
Source/binary release 20.1 (binaries to default to --with-mule=no).


1-April:
Source/binary release 20.2 (Mule and non-mule binaries).

These dates are not fixed and are open to discussion, but they are
within the ballpark of what I'd like to achieve.

Comments?
-- 
steve@miranova.com baur
Unsolicited commercial e-mail will be billed at $250/message.
"Bill Clinton is a bore.  He doesn't have a creative bone in his
body."  -- David Brinkley

