From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Juanma Barranquero Newsgroups: gmane.emacs.devel Subject: Re: FOR-RELEASE.W32 Date: Tue, 9 Aug 2005 14:44:43 +0200 Message-ID: References: <853bpjwiul.fsf@lola.goethe.zz> <42F87F87.7070209@student.lu.se> <42F8943A.5020007@gnu.org> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: sea.gmane.org 1123592299 24037 80.91.229.2 (9 Aug 2005 12:58:19 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 9 Aug 2005 12:58:19 +0000 (UTC) Cc: Lennart Borgman , Emacs Devel Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Aug 09 14:58:10 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1E2Tes-0001QR-DX for ged-emacs-devel@m.gmane.org; Tue, 09 Aug 2005 14:56:42 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1E2Thv-0001AZ-W2 for ged-emacs-devel@m.gmane.org; Tue, 09 Aug 2005 08:59:52 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1E2TgQ-0000Yw-5j for emacs-devel@gnu.org; Tue, 09 Aug 2005 08:58:18 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1E2TgM-0000Wz-OM for emacs-devel@gnu.org; Tue, 09 Aug 2005 08:58:16 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1E2TgJ-0000Rs-BJ for emacs-devel@gnu.org; Tue, 09 Aug 2005 08:58:12 -0400 Original-Received: from [64.233.182.204] (helo=nproxy.gmail.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1E2ThD-0002Pb-6L for emacs-devel@gnu.org; Tue, 09 Aug 2005 08:59:07 -0400 Original-Received: by nproxy.gmail.com with SMTP id h2so30224nfe for ; Tue, 09 Aug 2005 05:44:43 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=p0M0PK/Sw0k7M77uEsG5Qjd0vHPvqO7vpSr0b5/5yUl8V/kkv5hsLVYgkJmPztST6pWjRJiB0bPeB+qzaMzfhTvf/Jo8C73eBFwDVQCrvOY2mqvp4qKDY97jUv2Fc1k9f6lgQ3lHV0W7j0rfzdYDPMlwR04hkwNHfH815hOdrnE= Original-Received: by 10.48.144.1 with SMTP id r1mr197568nfd; Tue, 09 Aug 2005 05:44:43 -0700 (PDT) Original-Received: by 10.48.250.5 with HTTP; Tue, 9 Aug 2005 05:44:43 -0700 (PDT) Original-To: Jason Rumney In-Reply-To: <42F8943A.5020007@gnu.org> Content-Disposition: inline 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:41784 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:41784 On 8/9/05, Jason Rumney wrote: > These issues are being overblown. Not what I intended, for sure. > There are currently W32 specific > issues worthy of delaying a release, of Emacs in general, or of W32 > binaries. If there are issues worthy of delaying release, then they > belong in FOR-RELEASE. Sorry, this is a contradiction in terms. Per Richard's comments, stated publicly several times, there exists no such a thing as "w32 specific issues worthy of delaying a release of Emacs in general". > If they are not worthy of delaying release, then > they should be in a TODO file somewhere (a general one, or W32 specific > depending on the general consensus). OK. The general TODO is fine by me. > Lets not pretend that there is an > in between state of FOR-RELEASE.W32. That's another contradiction: You yourself, in the paragraph quoted above, have talked about things described as "w32-specific issues worthy of delaying of a release [...] of W32 binaries." What is the state for these issues, were they to exist? All in all, what I want is to keep track of the issues somewhere other than my e-mail client. TODO is fine. But let's be clear about it, then: either an issue is general, and can delay a general release, or it is Windows-specific, and can not delay even a binary release... --=20 /L/e/k/t/u