From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Evan Prodromou Newsgroups: gmane.lisp.guile.devel Subject: More Bug Stuff Date: Sun, 24 Mar 2002 14:23:17 -0600 Organization: GLUG (Guile Lovers Use Guile) http://www.glug.org/ Sender: guile-devel-admin@gnu.org Message-ID: <873cypn2a2.fsf@tyrell.bad-people-of-the-future.san-francisco.ca.us> NNTP-Posting-Host: localhost.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1017001639 6787 127.0.0.1 (24 Mar 2002 20:27:19 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 24 Mar 2002 20:27:19 +0000 (UTC) Original-Received: from fencepost.gnu.org ([199.232.76.164]) by main.gmane.org with esmtp (Exim 3.33 #1 (Debian)) id 16pEaF-0001lM-00 for ; Sun, 24 Mar 2002 21:27:19 +0100 Original-Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 16pEa3-0005HG-00; Sun, 24 Mar 2002 15:27:07 -0500 Original-Received: from cdm-208-140-220-brcs.cox-internet.com ([208.180.140.220] helo=tyrell) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 16pEXo-000577-00 for ; Sun, 24 Mar 2002 15:24:49 -0500 Original-Received: from evan by tyrell with local (Exim 3.34 #1 (Debian)) id 16pEWN-0003Gi-00 for ; Sun, 24 Mar 2002 14:23:19 -0600 Original-To: guile-devel@gnu.org X-PGP-Fingerprint: 1366 538C 1E7D 0093 C45B 1A50 A33C 1E7C 700A 0551 X-Revolutionary-Date: Quartidi, 4 Germinal 210 5:64:47 -29167 Original-Lines: 138 User-Agent: Gnus/5.090005 (Oort Gnus v0.05) Emacs/21.1 (i386-debian-linux-gnu) Errors-To: guile-devel-admin@gnu.org X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Developers list for Guile, the GNU extensibility library List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.lisp.guile.devel:181 X-Report-Spam: http://spam.gmane.org/gmane.lisp.guile.devel:181 OK, so, here's my collected bug file headers list. It gives the header name, arity (can be 0, 1, or Inf), and a description of what it's for. Let me know if I'm missing anything here. * Number (1) Identifying number for the bug, as an integer. Ex: Number: 12 * Title (1) Short descriptive title for the bug. Ex: Title: documentation mistakenly defines :autoload argument as expr and not list * Reported-By (0,1) Name and email address of person who reported the bug, in angle-bracket format. Ex: Reported-By: Evan Prodromou * Date-Reported (0,1) Date the bug was reported. Ex: Date-Reported: Sun, 24 Mar 2002 11:31:17 -0800 Date-Reported: 24 Mar 2002 All dates must either be in the above "standard" format, or in the format: dd Mon YYYY * Status (1) Status of the bug, in the format: status-val [(comment)] Here, status-val is one of: New, Unassigned, Assigned, Closed, Suspended, and comment is an optional comment. Status: New (received from bug-auto@gnu.org) Status: Suspended (unable to replicate error) Status: Closed * Priority (0,Inf) Priority of the bug, in this format: priority-val [[version=[version no]] (comment)] where priority-val is an integer between 1 and 10, and lower numbers are higher priority. The version number is the Guile branch or version where this is supposed to be fixed. For example, if a bug is of high priority to fix in 1.6, but not so high for 1.4, then the Priority headers would be: Priority: 8 version=1.4 (not severe enough to warrant work) Priority: 2 version=1.6 (crucial for release; talk to rlb) Priorities should be unique for a version. * Severity (0,1) How severe the bug is, in terms of what it does to the user. Field is: severity-val [(comment)] Where severity-val is one of: Wibni (meaning "Wouldn't it be nice if...") Theoretical (such as "Buffer overflow possible in guile-readline to get root") Nuisance (such as "There's no documentation on this function, so I had to experiment with it") Minor (such as "It doesn't work as advertised") Major (such as "It does damage") Fatal (such as "Guile killed my dog") ...and comment is an optional comment. For example: Severity: Nuisance (misspelling) Severity: Major (Memory leak) Severity: Minor Severity: Fatal (dumps core) NOTE that Priority and Severity are loosely coupled -- things that are more severe usually will have a high priority, but not necessarily. For example, updating the version string for a release is a high priority task, but it's not particularly severe (it'd be a nuisance). A bug that randomly causes backup tape explosions in the TI-99/4 port of Guile might have high severity, but a low priority. * Affects-Version (0,Inf) Versions of Guile affected by the bug. Affects-Version: 1.4 Affects-Version: 1.6.1 Affects-Version: 1.7 * Assigned-To (0,1) Name and email address of the person this bug is assigned to. Ex: Assigned-To: Marius Vollmer * Date-Fixed (0,Inf) Date the bug was fixed, in format: date-string version=vno Can be multiple if fixed in different branches. vno is the release version number that the fixed version should be available. Example: Date-Fixed: Sun, 24 Mar 2002 11:31:17 -0800 version=1.5.7 Date-Fixed: 05 Dec 1999 version=1.7.1 Date-Fixed: 12 Apr 2001 version=1.4.1 ~ESP -- Evan Prodromou evan@glug.org _______________________________________________ Guile-devel mailing list Guile-devel@gnu.org http://mail.gnu.org/mailman/listinfo/guile-devel