From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: Bug trackers
Date: Tue, 26 Feb 2008 15:00:31 -0500 [thread overview]
Message-ID: <jwvlk57a456.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <20080226193408.GM5438@volo.donarmstrong.com> (Don Armstrong's message of "Tue, 26 Feb 2008 11:34:08 -0800")
>> I started to play with the emacsbugs thingy (as Richard is stepping down
>> as maintainer and was basically doing the bug-tracking himself, I'm
>> eager to setup a "new" non-human bug-tracking system) and have some more
>> questions:
>>
>> - I see that right now, the address emacsbugs@lists.donarmstrong.com is
>> used only for the `emacs' package. Would it be possible to use it as
>> the default address for each and every package?
> Yes, that's just a setting in one of the configuration files. [The
> list of known packages is just a set of {packagename,maintainer}
> pairs.]
Then please do that.
>> - how can I manage the email address used as the maintainer of
>> a particular package? I see I can change the owner of a bug, but
>> I can't see how to manipulate the maintainer of a package.
> That's something that the debbugs administrator modifies; it's just
> the configuration file above.
OK, good. Since we don't know what packages we'll end up using, having
just a single catch-all address will take care of it for now.
>> - I see I can "create" a package as a side effect of reassigning a
>> bug to some inexistent package. What about deleting a package or
>> merging it with another one?
> You didn't actually create a package like that; you just assigned a
> bug to a non-existant package.[1]
I'm glad I can use non-existent packages like that. This will allow us
to try-and-use packages before knowing who should be the corresponding
maintainer (or maybe even without ever intending to assign a maintainer
address to it).
I see that `index-packages' does list those non-existent packages, so
other than not having any maintainer is there some downside to them?
> If you want to get rid of a package,
> you just reassign all of its bugs to a different package.
Good.
>> - As Richard mentioned, we would like/need to forward all
>> bug-reports sent to bug-gnu-emacs@gnu.org and
>> emacs-pretest-bug@gnu.org to submit@emacsbugs. But since these two
>> mailing-lists are also used currently for discussions, we would
>> only want to forward those email whose subject doesn't start with
>> "Re:".
> I'll skip that and any bugs with References: and In-Reply-To:.
Great.
>> The "Package" should always just be "Emacs" and the "Version" should
>> ideally be extracted from the subject (where it should appear in the
>> form: "Subject: <version>; <subject>") if present.
>> Can you arrange for that to happen?
> The Package: bit is already done; the version bit isn't taken care of,
> but it would be possible to do.
It will be good to do it, but it's not the top priority, so in case it's
a problem, we can leave it for later.
>> Can you arrange to do it directly on your end?
> Are those just mailing lists? If so, it's not that difficult.
Yes. You can subscribe to them via http://savannah.gnu.org/mail/?group=emacs
> 1: In the ack message you received, there should have been a warning
> about how the package didn't have a maintainer and probably isn't the
> right package; we don't currently disallow this because in Debian
> there are cases where the BTS is behind (usually less than 12 hours)
> on the set of packages that are actually uploaded.
It looks like a very handy "misfeature" for our use case ;-)
Stefan
PS: By the way, are you interested in this as an Emacs user as well, or
only as a debbugs developper?
next prev parent reply other threads:[~2008-02-26 20:00 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0802170200.m1H208hu013886@localhost.localdomain>
2008-02-18 5:25 ` Bug trackers Don Armstrong
2008-02-18 17:30 ` Richard Stallman
2008-02-18 23:28 ` Don Armstrong
2008-02-19 23:09 ` Richard Stallman
2008-02-19 23:18 ` Jason Rumney
2008-02-19 23:40 ` Karl Fogel
2008-02-21 2:00 ` Xavier Maillard
2008-02-21 22:28 ` Richard Stallman
2008-02-23 2:00 ` Xavier Maillard
2008-02-19 23:27 ` Don Armstrong
2008-02-20 16:44 ` Richard Stallman
2008-02-21 1:49 ` Don Armstrong
2008-02-21 21:24 ` Don Armstrong
2008-02-26 19:12 ` Stefan Monnier
2008-02-26 19:34 ` Don Armstrong
2008-02-26 20:00 ` Stefan Monnier [this message]
2008-02-26 21:23 ` Don Armstrong
2008-02-26 23:07 ` Stefan Monnier
2008-02-26 20:02 ` Stephen J. Turnbull
2008-02-27 16:08 ` Richard Stallman
2008-02-26 21:01 ` Jason Rumney
2008-02-26 21:17 ` Don Armstrong
2008-02-26 21:25 ` Stefan Monnier
2008-02-26 21:51 ` Jason Rumney
2008-02-26 23:00 ` Stefan Monnier
2008-02-26 23:02 ` Stephen J. Turnbull
2008-02-26 23:04 ` Jason Rumney
2008-02-14 4:42 Richard Stallman
2008-02-15 2:00 ` Xavier Maillard
2008-02-16 5:53 ` Richard Stallman
2008-02-17 2:00 ` Xavier Maillard
2008-02-16 8:40 ` Tassilo Horn
2008-02-16 9:16 ` Yoni Rabkin
2008-02-16 16:20 ` Tassilo Horn
2008-02-16 16:12 ` Manoj Srivastava
2008-02-16 16:53 ` Tassilo Horn
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvlk57a456.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).