From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Lars Magne Ingebrigtsen Newsgroups: gmane.emacs.devel Subject: Re: How does the Emacs bug tracker work? Date: Thu, 30 Jun 2011 23:22:59 +0200 Organization: Programmerer Ingebrigtsen Message-ID: References: <4E0C44A2.1040604@dogan.se> <874o37tqq2.fsf@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1309469233 17061 80.91.229.12 (30 Jun 2011 21:27:13 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 30 Jun 2011 21:27:13 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jun 30 23:27:08 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1QcOlQ-0006zM-EB for ged-emacs-devel@m.gmane.org; Thu, 30 Jun 2011 23:27:08 +0200 Original-Received: from localhost ([::1]:42921 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QcOlO-0005uL-UN for ged-emacs-devel@m.gmane.org; Thu, 30 Jun 2011 17:27:07 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:48761) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QcOhk-0004ul-2T for emacs-devel@gnu.org; Thu, 30 Jun 2011 17:23:21 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QcOhf-0007pn-IB for emacs-devel@gnu.org; Thu, 30 Jun 2011 17:23:19 -0400 Original-Received: from lo.gmane.org ([80.91.229.12]:50168) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QcOhe-0007pI-SC for emacs-devel@gnu.org; Thu, 30 Jun 2011 17:23:15 -0400 Original-Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1QcOhc-0005N7-NA for emacs-devel@gnu.org; Thu, 30 Jun 2011 23:23:12 +0200 Original-Received: from cm-84.215.51.58.getinternet.no ([84.215.51.58]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 30 Jun 2011 23:23:12 +0200 Original-Received: from larsi by cm-84.215.51.58.getinternet.no with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 30 Jun 2011 23:23:12 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: emacs-devel@gnu.org Original-Lines: 97 Original-X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: cm-84.215.51.58.getinternet.no Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAFVBMVEX28/Hj1s+MkKtRXofJ xso6LDoWChPD2FhYAAACTUlEQVQ4jX2TzXKbQBCEB8wDgIRzVmbBZ3mX1Zk/+ZyCzN4tmXn/R0gv SIlcTjJVINhvu6dnKVFX/L3oH+v/Af+0GlHd+HWd+pFH5r6vPklzgqIrx7IouvKzgMYsenXFWEDS jXgok6wccxpdb+zQFcZ8L3Yj97bZdandtWTYOmNeCzccad84UxV7S0MFUPUATRfBE0BTDI6ejgQF RzCuwLqhSozp9iuwzpljhgsbAdDtEBWDbZwbGr4DW7lhBchZYpK2HImyFuFxtVmbxEPEIEWCwrj3 2k7XcNXzjnsuDW5kWuwnup/AWsntJb+BPx45xZeEvoDUVfkqONOjE9FJ9UgxRbiBmyZT1QsRTuq6 gbsmBVA669LaFSTFrWFUaP4S9MNHgJS0TZcIQMtedaaHTHioQbp4q+lhOmR/DrpQDcX5d9/NCuAn nYNqui2kfoqtW0rDxO1Z9Xrb6hGQnkQONDA3z6ofUOc7m0H7g95U3ynFl051cR22wxbgPX+JDlB4 +jZHawx1qVcQE/XMdZ5671bFghxHhAkL1tkcUhHBHOh8lnBIdqILG8vmuN9ArZe9hitz0IljvdYi SmXzpsvsgkx8chZG6O4XrzRcTVDLEmDDblV4EYB65rA4F4ICeEjYbYAvLM57hcyxRC+sywxwNTMe I2BGIzayiLhALDUGCQBsDRROgjwAXYFzaIw3mWOPMJ8WAdHaOIsGGtNLBFPchZp5iokWhMQC8cki U6wr/iMxalg8NhLXbPELrwt7eADM0YCQr97AZGaJANOp6C8SMMHnnsoWvAAAAABJRU5ErkJggg== Mail-Copies-To: never X-Now-Playing: Various's _Cold Heat: Heavy Funk Rarities 1968-1974, Vol. 1_: "The Soul Seven - Mr. Chicken ---- (Alternate Take)" User-Agent: Gnus/5.110018 (No Gnus v0.18) Emacs/24.0.50 (gnu/linux) Cancel-Lock: sha1:zCCvy+MhfHBktJv/l+z814UFqyM= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-Received-From: 80.91.229.12 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:141285 Archived-At: Stefan Monnier writes: > I see bugs as being in a few different states: > - untriaged: we got the report and nothing else happened. > - inprogress: there's been at least one reply to it. > - stuck: like inprogress, but without activity because of lack of info. > - forgotten: like stuck, except that rather than a lack of info, there's > a lack of manpower. > - ready: there's a patch that fixes the problem and it looks like we > just have to double-check and/or cleanup the patch. > - fixed: that's what we like. > - wontfix: we don't think it's a bug, or we don't like the requested > feature and would hence oppose a patch if someone provides it. > - wishlist: not a bad idea, but noone cares enough to work on it. This is the actual metadata available on a bug: (pp (debbugs-get-status 5458) (current-buffer)) (((source . "unknown") (done . "Lars Magne Ingebrigtsen ") (found_versions) (blocks) (date . 1264225022) (fixed) (fixed_versions) (mergedwith) (found) (unarchived) (blockedby) (keywords "moreinfo") (summary) (msgid . "<871vhh7588.fsf@jidanni.org>") (id . 5458) (forwarded) (severity . "normal") (owner) (log_modified . 1309402441) (location . "db-h") (subject . "Unknown charset: ansi_x3.4-1968") (originator . "jidanni@jidanni.org") (last_modified . 1309402441) (pending . "done") (affects) (archived) (tags "moreinfo") (fixed_date) (package "emacs" "gnus") (found_date) (bug_num . 5458))) > These states map more or less to debbugs tags/severities: > - untriaged = "unclassified" > - inprogress = ??? > - stuck = "moreinfo" > - forgotten = ??? > - ready = "patch" > - fixed = "fixed" or "closed" > - wontfix = "notabug" or "wontfix" > - wishlist = "wishlist" > > I don't really know what "closed" should mean in this respect and don't > really care as long as I can easily select which above states I want > to see. The relevant stuff we can search for are package, severity and tag (and "archived", which is where I think "done" bugs up end after some days). So "closed" is mainly a way to say "I probably don't normally want to have these included in my searches". So moving three year old "wontfix"-es over to "closed" means taking less time searching for the bugs you want to look at. > The bad ones are "untriaged", "forgotten" and "ready", so we should come > up with a way to distinguish inprogress from untriaged, as well as a way > to mark the forgotten ones as well, so we can ask debbugs to show us > these ones. If `date' is the same as `log-modified', it means that nobody has responded to the bug. This can't be searched for, but can be highlighted in the debbugs buffer. > I guess we could add "inprogress" and "forgotten" tags and then try to > be careful to add "inprogress" whenever we first reply to a bug report. > Then have some cron job check all the "inprogress" bugs and turn them > into "forgotten" after some pre-defined delay (at which point humans > way come and relabel it to "moreinfo" if the delay is not our fault). Adding these tags aren't really necessary if using the debbugs.el interface. An "inprogress" report is one that has gotten at least one reply lately, and "forgotten" would be one where the reply is old. So this can be controlled client-side. If you don't consider 30 seconds being too slow to get the complete list of bugs over to Emacs. -- (domestic pets only, the antidote for overdose, milk.) bloggy blog http://lars.ingebrigtsen.no/