From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Alexis Newsgroups: gmane.emacs.devel Subject: Re: 4K Bugs Date: Fri, 08 Jan 2016 13:41:44 +1100 Message-ID: <87mvsgpzbr.fsf@gmail.com> References: <87mvszdp6b.fsf@gnus.org> <8737u9kv6f.fsf@russet.org.uk> <87oacwq240.fsf@gmail.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-Trace: ger.gmane.org 1452220932 6135 80.91.229.3 (8 Jan 2016 02:42:12 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 8 Jan 2016 02:42:12 +0000 (UTC) Cc: Emacs Development To: Richard Copley Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jan 08 03:42:08 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 1aHN0B-0003qA-4T for ged-emacs-devel@m.gmane.org; Fri, 08 Jan 2016 03:42:07 +0100 Original-Received: from localhost ([::1]:33785 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aHN0A-0004t5-H8 for ged-emacs-devel@m.gmane.org; Thu, 07 Jan 2016 21:42:06 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:33776) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aHMzy-0004t0-E3 for emacs-devel@gnu.org; Thu, 07 Jan 2016 21:41:55 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aHMzv-0001lb-8Q for emacs-devel@gnu.org; Thu, 07 Jan 2016 21:41:54 -0500 Original-Received: from mail-pf0-x232.google.com ([2607:f8b0:400e:c00::232]:33764) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aHMzv-0001l7-24 for emacs-devel@gnu.org; Thu, 07 Jan 2016 21:41:51 -0500 Original-Received: by mail-pf0-x232.google.com with SMTP id e65so2584647pfe.0 for ; Thu, 07 Jan 2016 18:41:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:from:to:cc:subject:in-reply-to:date:message-id :mime-version:content-type; bh=VT98AJE4guo6djh3DjD6ixB5dCd92v3/2lStbLqSClg=; b=CZwwGU6QjRWLAPAVBi0lodpszf+RGcAYqAHu1FZcDfUWeuoqBcNp4D2AfZ23LOlFd9 GngtiNgU8KYuRdqv012jJ7lnOy1oJ3IVdeQ4XIDUN66Mg0+PBP7MviHVjfyQj1sOsQwH GSehnXnj2W07WdVi25SrT4uwcfBH8Z074wJ8daYbqGaSCdaHifWYEHorTtrp12Po8hwr mINeLQdbb2h+pJctEfPIh5YJDnbsJEKuQfxfhcZ8ap2cyls8xurXqEv7c/139AogHr7T aKeNpKTDEUp2cDJfich7W1zYScS7vEvIVY2NUrnLi9RMo0gcBQ16rC0/iKBsJKe/lAAS pqHA== X-Received: by 10.98.68.152 with SMTP id m24mr1055085pfi.78.1452220910424; Thu, 07 Jan 2016 18:41:50 -0800 (PST) Original-Received: from localhost (114-198-94-242.dyn.iinet.net.au. [114.198.94.242]) by smtp.gmail.com with ESMTPSA id u21sm597430pfi.15.2016.01.07.18.41.48 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 07 Jan 2016 18:41:49 -0800 (PST) In-reply-to: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2607:f8b0:400e:c00::232 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:197795 Archived-At: Richard Copley writes: >> An argument could be made that the longest-outstanding issues >> should be displayed first, to try to encourage their >> resolution. Having said that, it could also be argued that >> their longevity means they're less likely to be able to be >> resolved soon than recent bugs. So i'm not sure what the best >> default is here. > > This problem will go away by itself now that we're deluged with > enthusiastic triagers. Heh, well, i wouldn't call the (from what i can tell) maybe-less-than-half-a-dozen of us to be a "deluge". :-) At any rate, i'm not sure the problem will necessarily go away by itself, for a few reasons: * Looking over the longest-outstanding bugs, i noticed a number of them were Mac-specific. As i don't have access to a Mac - i'm on Debian - i can't try to reproduce the issue. So unless triagers have access to a Mac, such issues are more likely to languish. (This had made me wonder whether tags like 'mac', 'win' etc. might be useful?) * Even triagers who do have access to a Mac won't necessarily feel competent enough to try to address /every/ long-outstanding bug; and this applies more generally, regardless of OS. i've been following bug-gnu-emacs for a while now, to try to help triage new bugs, but i only address a small fraction of those that come through: those haven't been addressed by someone more expert than me, and which i understand well enough to be able to try to reproduce and/or ask (hopefully) sensible questions about. * Some of the long-outstanding bugs have a complicated history that is daunting to try to untangle and work out what the next step might be. Particularly when the history involves a heated debate which has apparently reached an uncomfortable stalemate. Regarding the last point: maybe at least some of these sorts of bugs could be brought to John's attention for arbitration? Alexis.