From xemacs-m  Sun Jan  5 15:58:30 1997
Received: from altair.xemacs.org (steve@xemacs.miranova.com [206.190.83.19])
          by xemacs.cs.uiuc.edu (8.8.4/8.8.4) with ESMTP
	  id PAA12622 for <xemacs-beta@xemacs.org>; Sun, 5 Jan 1997 15:58:29 -0600 (CST)
Received: (from steve@localhost)
          by altair.xemacs.org (8.8.4/8.8.4)
	  id OAA08072; Sun, 5 Jan 1997 14:08:45 -0800
Sender: steve@xemacs.org
To: xemacs-beta@xemacs.org
Subject: Re: XEmacs 20.0-b34 is released
References: <m2k9ps3hae.fsf@altair.xemacs.org> 	<199701050420.XAA07275@spacely.icd.teradyne.com> <199701051748.KAA02986@branagh.lanl.gov>
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: John Turner's message of Sun, 5 Jan 1997 10:48:50 -0700
Mime-Version: 1.0 (generated by tm-edit 7.100)
Content-Type: text/plain; charset=US-ASCII
Date: 05 Jan 1997 14:08:44 -0800
Message-ID: <m2iv5bvkpf.fsf@altair.xemacs.org>
Lines: 46
X-Mailer: Red Gnus v0.72/XEmacs 20.0

>>>>> "John" == John Turner <turner@xdiv.lanl.gov> writes:

John> [coming in kinda late on this; tried to pick one of the last msgs in
John> the thread to follow up to...]

No you're not late.  We need more discussion on this.  I am quite open
to suggestions.

John> Several thoughts:

John> o There was less discussion on the "should we release 19.15" question
John>   than I had expected, back when Steve asked.

John> o Although at the time I was pushing for a 19.15 release, I have
John>   to say that if 20.0 really is virtually ready to go, then
John>   maybe a 19.15 release should indeed be scuttled.  But I for
John>   one have never even built a 20.0 beta.  And I've seen more
John>   crash reports for 20.0 than for 19.15 (I don't recall any for
John>   19.15 for a while).

An alternative is to push 20.0 into the first or second week of
February.  I don't think we can avoid shortening the interval between
releases of v20.  We can also move my suggested date for 19.15 release
forward.  That would give 3 to 4 weeks between 19.15 and 20.0.

John> o I do think simultaneous release is a bad idea.

I gathered that was what Chuck's original plans were.  I am
indifferent either way.  Assuming that we release 19.15 next week say,
and 20.0 the first week of February, and there needs to be a 19.16
maintenance release when would you suggest releasing it?

John> Steve, I know you tried to resolve this a month or so ago, but
John> maybe it's worth talking about again.  If 19.15 is canned, then
John> I (and everybody else) need(s) to start working out 20.0 with a
John> vengance...

If 19.15 is as stable as it looks, I am quite agreeable to stop
fiddling around with it and release it next week(end).

(Trying to shut up on this thread so as to not stifle commentary).
-- 
steve@miranova.com baur
Unsolicited commercial e-mail will be billed at $250/message.
"That Bill Clinton.  He probably doesn't know how to log on to the
Internet."  -- Rush Limbaugh, noted Computer Expert

