From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Thien-Thi Nguyen Newsgroups: gmane.lisp.guile.devel Subject: Re: Tool version in HACKING Date: Tue, 09 Apr 2002 23:29:52 -0700 Sender: guile-devel-admin@gnu.org Message-ID: References: <87adscre31.fsf@zagadka.ping.de> <200204091928.MAA18069@onyx.he.net> Reply-To: ttn@glug.org NNTP-Posting-Host: localhost.gmane.org X-Trace: main.gmane.org 1018420590 15355 127.0.0.1 (10 Apr 2002 06:36:30 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 10 Apr 2002 06:36:30 +0000 (UTC) Cc: mvo@zagadka.ping.de, guile-devel@gnu.org Return-path: Original-Received: from fencepost.gnu.org ([199.232.76.164]) by main.gmane.org with esmtp (Exim 3.33 #1 (Debian)) id 16vBiX-0003zY-00 for ; Wed, 10 Apr 2002 08:36:29 +0200 Original-Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 16vBi8-0003TC-00; Wed, 10 Apr 2002 02:36:04 -0400 Original-Received: from ca-crlsbd-u4-c4c-174.crlsca.adelphia.net ([68.66.186.174] helo=giblet) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 16vBgB-0003Py-00 for ; Wed, 10 Apr 2002 02:34:04 -0400 Original-Received: from ttn by giblet with local (Exim 3.33 #1 (Debian)) id 16vBc8-0006ne-00; Tue, 09 Apr 2002 23:29:52 -0700 Original-To: ghouston@arglist.com In-Reply-To: <200204091928.MAA18069@onyx.he.net> (message from Gary Houston on 9 Apr 2002 20:28:25 +0100) Errors-To: guile-devel-admin@gnu.org X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.0.9 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:348 X-Report-Spam: http://spam.gmane.org/gmane.lisp.guile.devel:348 From: Gary Houston Date: 9 Apr 2002 20:28:25 +0100 The versions seemed a bit out of date, and the last policy I remember is that the latest released versions are always used. Since it's easy to find out what the versions are, it doesn't seem necessary to list them in the file and saves the confusion when the released versions differ from the file versions (is the file correct or did somebody just forget to update it?) for the most part the HACKING tools are stable; we've run accross weirdness (recently and also going back, considering some of the comments in the input files), but over time the tools live up to their documentation. to be precise and do minimal work, we need to record version numbers only for problematic cases. this means every time there's a tool bug discovered, HACKING needs to be updated, otherwise the default stance (which we need to state explicitly) of "latest is greatest" holds. we need to also remind people to check their tool distributor's policy and practice. btw, in fixing this bug we come to the process question of: how do bugs fit into the TODO list? one obvious answer is "don't use TODO list, bug fixing (for those deemed needing it) is best managed separately". this is a not wholistic view however; bug fixing takes time which directly affects what can be done on TODO. fundamentally, bug fixing is a (we hope) non-repetitive action, something to do when the time is right. (and if the particular fix is congruent w/ long term design, the fix could be called one-shot.) so i think it would be useful to consider ways to include bugs in the TODO list. what does everyone think about this protocol: - discuss bug - someone proposes fix - agree on fix - add to TODO "NAME: FIX-ACTION" (or just "NAME" and use another level to enumerate fix-action subtasks) under "Fix Bugs" (a new top-level) - if a bug moves for whatever reason (for example under "Guile 1.6"), it needs to be put under another "Fix Bugs" parent ? the basic characteristic here is that only bugs whose fixes are known are added to TODO, and bug fix parent task is always easy to identify. this helps keep TODO focus probably and definitely makes downstream tools happy. thi _______________________________________________ Guile-devel mailing list Guile-devel@gnu.org http://mail.gnu.org/mailman/listinfo/guile-devel