From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Jason Rumney Newsgroups: gmane.emacs.devel Subject: Re: FOR-RELEASE.W32 Date: Tue, 09 Aug 2005 11:02:12 +0100 Message-ID: <42F87F24.2030603@gnu.org> References: <853bpjwiul.fsf@lola.goethe.zz> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0329769229==" X-Trace: sea.gmane.org 1123582366 28368 80.91.229.2 (9 Aug 2005 10:12:46 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 9 Aug 2005 10:12:46 +0000 (UTC) Cc: Juanma Barranquero , Emacs Devel Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Aug 09 12:12:43 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1E2R5H-0007gz-6D for ged-emacs-devel@m.gmane.org; Tue, 09 Aug 2005 12:11:47 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1E2R8K-0004Wc-Ev for ged-emacs-devel@m.gmane.org; Tue, 09 Aug 2005 06:14:56 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1E2Qxt-0001S9-V1 for emacs-devel@gnu.org; Tue, 09 Aug 2005 06:04:10 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1E2Qxq-0001Qx-3R for emacs-devel@gnu.org; Tue, 09 Aug 2005 06:04:08 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1E2Qxp-0001QQ-7a for emacs-devel@gnu.org; Tue, 09 Aug 2005 06:04:05 -0400 Original-Received: from [217.207.198.106] (helo=exchange.integrasp.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1E2R89-0006Nm-CG; Tue, 09 Aug 2005 06:14:45 -0400 Original-Received: from ASSP-nospam (localhost [127.0.0.1]) by exchange.integrasp.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id 37Q0TM4P; Tue, 9 Aug 2005 10:57:26 +0100 Original-Received: from 10.10.5.77 ([10.10.5.77] helo=[10.10.5.77]) by ASSP-nospam ; 9 Aug 05 09:57:25 -0000 User-Agent: Mozilla Thunderbird 1.0.5 (Windows/20050711) X-Accept-Language: en-us, en Original-To: David Kastrup In-Reply-To: <853bpjwiul.fsf@lola.goethe.zz> X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:41762 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:41762 This is a multi-part message in MIME format. --===============0329769229== Content-Type: multipart/alternative; boundary="------------060303040200020501030808" This is a multi-part message in MIME format. --------------060303040200020501030808 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit David Kastrup wrote: >Juanma Barranquero writes: > > >>As Richard has said that Emacs-on-Windows problems shouldn't delay >>the release, Lennart and I have been thinking of adding a file >>(tentatively named admin/FOR-RELEASE.W32) listing things that would >>be nice to have before releasing a binary tarball for Windows. >> >> > >Personally, I think really bad problems on Windows should at least >delay the release of a Windows binary: > > None of these problems make Emacs unusable. The JPEG problem can be avoided by compiling with a Free compiler (which we do anyway for binary releases). The high CPU usage for server sockets can be avoided by not using server sockets. Perhaps that means we continue to recommend gnuserv to Windows users in 22.1, but it should not mean that we withhold Emacs binaries for a much awaited version with many improvements over 21.x. --------------060303040200020501030808 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit David Kastrup wrote: 
Juanma Barranquero <lekktu@gmail.com> writes:
  
As Richard has said that Emacs-on-Windows problems shouldn't delay
the release, Lennart and I have been thinking of adding a file
(tentatively named admin/FOR-RELEASE.W32) listing things that would
be nice to have before releasing a binary tarball for Windows.
    

Personally, I think really bad problems on Windows should at least
delay the release of a Windows binary:
None of these problems make Emacs unusable. The JPEG problem can be avoided by compiling with a Free compiler (which we do anyway for binary releases). The high CPU usage for server sockets can be avoided by not using server sockets. Perhaps that means we continue to recommend gnuserv to Windows users in 22.1, but it should not mean that we withhold Emacs binaries for a much awaited version with many improvements over 21.x.

--------------060303040200020501030808-- --===============0329769229== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Emacs-devel mailing list Emacs-devel@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-devel --===============0329769229==--