From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Tassilo Horn Newsgroups: gmane.emacs.devel Subject: Re: Bug statistics Date: Sat, 26 Jun 2010 11:28:49 +0200 Message-ID: <201006261128.50509.tassilo@member.fsf.org> References: <1focf1eb1p.fsf@fencepost.gnu.org> <87vd9623zn.fsf@red-bean.com> <83zkyicgzh.fsf@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-Trace: dough.gmane.org 1277544851 27506 80.91.229.12 (26 Jun 2010 09:34:11 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sat, 26 Jun 2010 09:34:11 +0000 (UTC) Cc: Karl Fogel To: emacs-devel@gnu.org, Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jun 26 11:34:07 2010 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1OSRm2-0002Tc-Pi for ged-emacs-devel@m.gmane.org; Sat, 26 Jun 2010 11:34:07 +0200 Original-Received: from localhost ([127.0.0.1]:41630 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OSRm1-0002zd-CS for ged-emacs-devel@m.gmane.org; Sat, 26 Jun 2010 05:34:05 -0400 Original-Received: from [140.186.70.92] (port=37214 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OSRln-0002sG-1D for emacs-devel@gnu.org; Sat, 26 Jun 2010 05:33:52 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OSRh1-0005n3-Sw for emacs-devel@gnu.org; Sat, 26 Jun 2010 05:28:56 -0400 Original-Received: from out1.smtp.messagingengine.com ([66.111.4.25]:48169) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OSRgz-0005mY-Jx; Sat, 26 Jun 2010 05:28:53 -0400 Original-Received: from compute1.internal (compute1.internal [10.202.2.41]) by gateway1.messagingengine.com (Postfix) with ESMTP id 11FC31071FC; Sat, 26 Jun 2010 05:28:53 -0400 (EDT) Original-Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Sat, 26 Jun 2010 05:28:53 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=from:to:subject:date:cc:references:in-reply-to:mime-version:content-type:content-transfer-encoding:message-id; s=smtpout; bh=wabruZwPPwqw76874QKbEoMlNSY=; b=iAz/0QnL7Rv52LXEvON6c87oHNQt3wuZdbX2FquV37ZPZVRAoMjdZvIoa2StEKxKXvqJZ5KHG3Ygd+/1yUeXCnPeHOPTxJ0k2mBytcIIEh+B82J9abHF1ZZzhW1SxTSuoy7fX8taajI3zjcHk4kiQTW3SqMBwZF2xPiZAutgIlU= X-Sasl-enc: 40A0WHwd5PaBmsbehSrbGJmkAaXLkvn+oCuJwSLKS8m0 1277544532 Original-Received: from thinkpad.localnet (p54AF0358.dip0.t-ipconnect.de [84.175.3.88]) by mail.messagingengine.com (Postfix) with ESMTPSA id A642F169B5; Sat, 26 Jun 2010 05:28:52 -0400 (EDT) User-Agent: KMail/1.13.3 (Linux/2.6.34-gentoo-r1; KDE/4.4.4; x86_64; ; ) In-Reply-To: <83zkyicgzh.fsf@gnu.org> X-Face: `TY6r/ws=N5uqO1E`M=Sups<}n%T[E^o_?MJj 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:126423 Archived-At: On Saturday 26 June 2010 10:53:22 Eli Zaretskii wrote: > > FWIW, when I've experienced this automated dup-finding in the web > > interface of other bug trackers, it has not been a nuisance -- on > > the contrary it was a great relief, because it helped me know I'm > > not wasting the developers' time with a duplicate report. (The > > majority of the time, it did find a dup of what I was about to file. > > Sometimes I was able to go to that existing report and add useful > > information.) > > > > For me it became one of those "never go back" features, like sexp > > motion in Emacs. > > That would put you into the ``have a lot of time on your hands'' > category, in my book. I have maybe 10 hours a week to work on Emacs. > I cannot invest any significant portion of that time on reading the > descriptions of bugs, without adversely affecting my productivity, > which is too low as it is. Well, you (as developer) should use your limited time to fix the bugs for which users have spent their limited time for reporting. If users do that carefully by avoiding dupes, linking related bug and adding as much information as possible, then you can spend your time much more effectively. And because a thoroughly reported bug is much more likely to become fixed quickly, the user has a reward, too. Looks like a win-win situation to me. Bye, Tassilo