From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: [Emacs-diffs] emacs-25 d0d9f55: Allow newlines inside cl function arglists Date: Fri, 13 May 2016 11:47:56 +0300 Message-ID: <83ziru8htv.fsf@gnu.org> References: <20160509235343.17047.73943@vcs.savannah.gnu.org> <20160509235343.759D0220128@vcs.savannah.gnu.org> <83inyj9j1z.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1463129302 10214 80.91.229.3 (13 May 2016 08:48:22 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 13 May 2016 08:48:22 +0000 (UTC) Cc: dgutov@yandex.ru, emacs-devel@gnu.org To: John Wiegley Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri May 13 10:48:21 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1b18lg-0007lt-Ct for ged-emacs-devel@m.gmane.org; Fri, 13 May 2016 10:48:20 +0200 Original-Received: from localhost ([::1]:33466 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b18lf-0007L3-OQ for ged-emacs-devel@m.gmane.org; Fri, 13 May 2016 04:48:19 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:50125) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b18lY-0007CT-V7 for emacs-devel@gnu.org; Fri, 13 May 2016 04:48:14 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1b18lU-0005W1-6W for emacs-devel@gnu.org; Fri, 13 May 2016 04:48:11 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:33893) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b18lE-0005SW-J6; Fri, 13 May 2016 04:47:52 -0400 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:4623 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1b18l5-0003Go-F4; Fri, 13 May 2016 04:47:51 -0400 In-reply-to: (message from John Wiegley on Thu, 12 May 2016 14:23:05 -0700) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:203819 Archived-At: > From: John Wiegley > Cc: emacs-devel@gnu.org, dgutov@yandex.ru, larsi@gnus.org, ahyatt@gmail.com, arturmalabarba@gmail.com, acm@muc.de > Date: Thu, 12 May 2016 14:23:05 -0700 > > A bug should be considered release blocking for 25.1 if: > > 1. It causes loss of user data. > > 2. It renders core functionality unusable without any acceptable workaround. > This includes: crashing, hanging, runaway memory consumption, exhaustion > of limited resources such as file handles, etc. > > The extent of "core" is open to debate, but basically I mean features > used by a great many users. > > 3. The presence of the bug makes basic functionality annoying or cumbersome. > > 4. The presence of the bug would cause widespread breakage in community > packages, unless there is an acceptable upgrade path. > > 5. It impairs the goals of the Free Software Foundation. Thanks. However, items 3 and 4 are IMO too vague, and can fit almost any issue, as the criteria are open to subjective interpretation. Also, we used to have criteria related to the age of the bug, on the assumption that old bugs are less likely to be critical. I'm not saying that we must keep such a criterion, but I think it should at least be considered for inclusion. > In other words, as long as the presence of bug X doesn't make Emacs unsuitable > for use, I'm willing to live with bug X until the next point release. This sounds like much more stringent criterion than the others.