From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Unanswered Emacs Problem Reports 40+ Months Date: Thu, 24 Oct 2013 10:21:51 -0400 Message-ID: References: <52689833.7060109@gnulinuxlibre.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; CHARSET=US-ASCII Content-Transfer-Encoding: 7BIT X-Trace: ger.gmane.org 1382624535 30548 80.91.229.3 (24 Oct 2013 14:22:15 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 24 Oct 2013 14:22:15 +0000 (UTC) Cc: Christian Bryant , emacs-devel@gnu.org To: Glenn Morris Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Oct 24 16:22:17 2013 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 1VZLnj-0004Jf-Ka for ged-emacs-devel@m.gmane.org; Thu, 24 Oct 2013 16:22:15 +0200 Original-Received: from localhost ([::1]:54679 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VZLnj-0003MJ-6p for ged-emacs-devel@m.gmane.org; Thu, 24 Oct 2013 10:22:15 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:58667) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VZLnT-00035N-FF for emacs-devel@gnu.org; Thu, 24 Oct 2013 10:22:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VZLnM-00006D-5x for emacs-devel@gnu.org; Thu, 24 Oct 2013 10:21:59 -0400 Original-Received: from relais.videotron.ca ([24.201.245.36]:45884) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VZLnM-000067-3K; Thu, 24 Oct 2013 10:21:52 -0400 Original-Received: from ceviche.home ([24.201.53.56]) by VL-VM-MR006.ip.videotron.ca (Oracle Communications Messaging Exchange Server 7u4-22.01 64bit (built Apr 21 2011)) with ESMTP id <0MV600HTTFWFR7B0@VL-VM-MR006.ip.videotron.ca>; Thu, 24 Oct 2013 10:21:51 -0400 (EDT) Original-Received: by ceviche.home (Postfix, from userid 20848) id 8956E6609A; Thu, 24 Oct 2013 10:21:51 -0400 (EDT) In-reply-to: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Solaris 10 X-Received-From: 24.201.245.36 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:164513 Archived-At: > Would this be a totally automatic process, in which every old, open bug > report simply gets a mail asking the OP to confirm it is still relevant? I think so, yes. > Because I'm not sure that is a very useful thing to do. I don't like it > when eg certain distributions automatically close all bugs filed against > previous releases unless people confirm they still exist in the latest > release. We're not talking about closing the bugs, but confirming that the bug is still relevant. Tho, in the absence of a reply by the bug-submitter within a month (say), we could also decide to close the bug. > If every person with commit access to Emacs dealt with 15 bugs, > that would be all of them. ;) The idea is to ask the bug-submitter's help. I think it would also help to try and classify those old bugs into different categories: - bugs that are waiting for more info from the submitter. - bugs to which we did reply and then things stalled (e.g. because we don't know how to fix them, lack of manpower, ...). - bugs that have not seen any activity at all: not even a "hmm, thanks, we'll look into it". These then get subdivided into: - author is a well-known contributor, so it's acceptable. - else, this is a serious lack of consideration, we should at least tell him "thank you for reporting this problem and sorry we don't have the manpower to handle it". I think this classification can be made automatically/heuristically by checking if the last message was from a developer. Stefan