From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Don Armstrong Newsgroups: gmane.emacs.devel Subject: Re: Debbugs testbed Date: Thu, 28 Feb 2008 23:16:18 -0800 Message-ID: <20080229071618.GJ2110@volo.donarmstrong.com> References: <18375.32881.925479.598407@kahikatea.snap.net.nz> <20080229040138.GU7406@rzlab.ucr.edu> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 X-Trace: ger.gmane.org 1204269401 11036 80.91.229.12 (29 Feb 2008 07:16:41 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 29 Feb 2008 07:16:41 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Feb 29 08:17:06 2008 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.50) id 1JUzUO-0007cE-1c for ged-emacs-devel@m.gmane.org; Fri, 29 Feb 2008 08:17:04 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JUzTr-0008OS-BL for ged-emacs-devel@m.gmane.org; Fri, 29 Feb 2008 02:16:31 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JUzTm-0008OD-HI for emacs-devel@gnu.org; Fri, 29 Feb 2008 02:16:26 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JUzTk-0008O1-L2 for emacs-devel@gnu.org; Fri, 29 Feb 2008 02:16:25 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JUzTk-0008Ny-DR for emacs-devel@gnu.org; Fri, 29 Feb 2008 02:16:24 -0500 Original-Received: from rzlab.ucr.edu ([138.23.92.77]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1JUzTk-0002xm-0v for emacs-devel@gnu.org; Fri, 29 Feb 2008 02:16:24 -0500 Original-Received: from rzlab.ucr.edu (rzlab.ucr.edu [127.0.0.1]) by rzlab.ucr.edu (8.13.8/8.13.8/Debian-3) with ESMTP id m1T7GPhi027132 for ; Thu, 28 Feb 2008 23:16:25 -0800 Original-Received: (from remotemail@localhost) by rzlab.ucr.edu (8.13.8/8.13.8/Submit) id m1T7GP1Q027131 for emacs-devel@gnu.org; Thu, 28 Feb 2008 23:16:25 -0800 Original-Received: (nullmailer pid 4629 invoked by uid 1000); Fri, 29 Feb 2008 07:16:19 -0000 Mail-Followup-To: emacs-devel@gnu.org Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17+20080114 (2008-01-14) X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 3) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." 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:90839 Archived-At: On Thu, 28 Feb 2008, Stefan Monnier wrote: > Yes, that would be good. I've used the "index packages" command, but > it would make sense to have it available from the web page as well. I've renabled it. (I used the default apache configuration which denies it from most hosts.) > > The 'release-critical' url is also specific to Debian, but what > > usually is present there can also be set up for emacs once the > > maintainers decide what bugs qualify as release critical. ;-) > > That might indeed be helpful. Tho I'm not sure how that would work. > E.g. how can I specify that it's release-critical for Emacs-22.2 > rather than release-critical for Emacs-23.1? The way this is typically done is by severity+versioning. So bugs of severity > than a certain level are release critical; you can indicate whether a bug is fixed or not in a particular version using the version tracking. [That is, you would either close the bug with a Version pseudoheader, or use fixed foobug fooversion; in a command to control.] Then, assuming the BTS knows what version of the 22 series 23.1 is a decendant of, bugs that are fixed there are automatically marked fixed in all decendants of that version, but are still marked buggy all decendants of an unfixed version (and unknown in all other versions.) [It may be worthwhile to tie this to VCS versions, but the code to do that integration isn't there.[1]] You can see the graphs of what I'm talking about for a semi-complex package in Debian here: http://tinyurl.com/2mtud7 [2] > >> I'm presuming now if I send my previous reports using > >> report-emacs-bug that they will end up in the database. Is that > >> right? > > I believe this is not yet the case. Don? AFAICT, that's not yet the case. It's basically waiting for one of the mail administrators to put in the hook to send bugs, or for me to do it manually. Don Armstrong 1: And I would really need to think out what the right method of handling the correspondance between a VCS version and a release version. 2: http://bugs.debian.org/cgi-bin/version.cgi?info=1;width=;found=21.3%2B1-5;found=21.3%2B1-8;found=emacs21%2F21.4a-3;height=;package=emacs21;format=png;collapse=1;ignore_boring=0 -- Taxes are not levied for the benefit of the taxed. -- Robert Heinlein _Time Enough For Love_ p250 http://www.donarmstrong.com http://rzlab.ucr.edu