From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Glenn Morris Newsgroups: gmane.emacs.devel Subject: Re: Unanswered Emacs Problem Reports 40+ Months Date: Thu, 24 Oct 2013 03:46:37 -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 X-Trace: ger.gmane.org 1382600802 4438 80.91.229.3 (24 Oct 2013 07:46:42 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 24 Oct 2013 07:46:42 +0000 (UTC) Cc: emacs-devel@gnu.org To: Christian Bryant Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Oct 24 09:46:46 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 1VZFcz-00012F-Pk for ged-emacs-devel@m.gmane.org; Thu, 24 Oct 2013 09:46:46 +0200 Original-Received: from localhost ([::1]:52984 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VZFcx-00042B-7O for ged-emacs-devel@m.gmane.org; Thu, 24 Oct 2013 03:46:43 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:49236) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VZFct-00041t-Tm for emacs-devel@gnu.org; Thu, 24 Oct 2013 03:46:41 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VZFcs-00046k-J9 for emacs-devel@gnu.org; Thu, 24 Oct 2013 03:46:39 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:46582) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VZFcs-00046f-Fs for emacs-devel@gnu.org; Thu, 24 Oct 2013 03:46:38 -0400 Original-Received: from rgm by fencepost.gnu.org with local (Exim 4.71) (envelope-from ) id 1VZFcr-0001ET-Ks; Thu, 24 Oct 2013 03:46:37 -0400 X-Spook: USCOI quarter counter intelligence AIMSX Bush Wired X-Ran: bS16,n5v}qZcst+~zV$ZSFn[h#`V(y(Ca}jgXm+;_xw/tGT&GF?P=@g (Christian Bryant's message of "Wed, 23 Oct 2013 20:46:59 -0700") User-Agent: Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/) X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2001:4830:134:3::e 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:164503 Archived-At: Christian Bryant wrote: > I'll be embarking on a contact effort over the next month to query > problem reports for Emacs from oldest on up as to whether the bug is > still relevant, and if not, request that reporters please close the > report. If the bug _is_ still relevant, I'll ask them to update the > bug report. This effort will apply to bugs older than 40 months, > starting with the oldest reports, as noted in recent tracker data [1]. Thanks. We certainly need help with bug reports. I'm not exactly sure what you are proposing to do, though. 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? 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. > I'll make no initial attempt to cross-reference bugs for duplication, > fixes in later releases, or other troubleshooting efforts. See, I kind of think this is the thing that _should_ be done first (I've tried to do it in the past). Once someone has filed a bug, the burden is on us as developers to do something about it. Whether that's requesting more info, fixing it, saying we won't fix it, saying it's not a bug, or saying that it's not a priority right now. I don't really know what's going to happen with all the old Emacs bugs that are still open. It seems impossible to ever fix them all. But does that mean we should just declare bankruptcy and close them? I don't know... If every person with commit access to Emacs dealt with 15 bugs, that would be all of them. ;) Sometimes I look through the old ones and see if I can do anything about them. I do think this requires actually reading them, though, not simply sending a form email.