From: Don Armstrong <don@donarmstrong.com>
To: emacs-devel@gnu.org
Subject: Re: Debbugs testbed
Date: Thu, 28 Feb 2008 23:16:18 -0800 [thread overview]
Message-ID: <20080229071618.GJ2110@volo.donarmstrong.com> (raw)
In-Reply-To: <jwvk5ko4b06.fsf-monnier+emacs@gnu.org>
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
next prev parent reply other threads:[~2008-02-29 7:16 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-29 3:48 Debbugs testbed Nick Roberts
2008-02-29 4:01 ` Don Armstrong
2008-02-29 4:57 ` Stefan Monnier
2008-02-29 6:00 ` Bill Wohler
2008-02-29 7:16 ` Don Armstrong [this message]
2008-03-02 21:53 ` Stefan Monnier
-- strict thread matches above, loose matches on Subject: below --
2008-02-20 2:18 Don Armstrong
2008-02-20 4:56 ` Óscar Fuentes
2008-02-20 5:07 ` Nick Roberts
2008-02-20 5:20 ` Óscar Fuentes
2008-02-20 5:31 ` Miles Bader
2008-02-20 5:43 ` Óscar Fuentes
2008-02-20 7:16 ` Don Armstrong
2008-02-20 9:09 ` Tassilo Horn
2008-02-20 10:12 ` Mathias Dahl
2008-02-20 10:44 ` Walter Franzini
2008-02-21 2:00 ` Xavier Maillard
2008-02-21 9:29 ` Walter Franzini
2008-02-21 22:29 ` Richard Stallman
2008-02-22 2:00 ` Xavier Maillard
2008-02-22 8:11 ` Don Armstrong
2008-02-23 2:00 ` Xavier Maillard
2008-02-20 13:46 ` Óscar Fuentes
2008-02-20 14:06 ` Jason Rumney
2008-02-20 16:26 ` Stefan Monnier
2008-02-20 16:05 ` Manoj Srivastava
2008-02-20 16:44 ` Richard Stallman
2008-02-20 21:41 ` Stephen J. Turnbull
2008-02-20 11:46 ` Thien-Thi Nguyen
2008-02-21 2:00 ` Xavier Maillard
2008-02-20 16:44 ` Richard Stallman
2008-02-21 1:49 ` Don Armstrong
2008-02-20 20:29 ` Stefan Monnier
2008-02-21 20:45 ` James Cloos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080229071618.GJ2110@volo.donarmstrong.com \
--to=don@donarmstrong.com \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.