From: Manoj Srivastava <srivasta@ieee.org>
To: emacs-devel@gnu.org
Subject: Re: Moving to the new infrastructure
Date: Wed, 23 Jan 2008 10:41:29 -0600 [thread overview]
Message-ID: <871w88lcjq.fsf@anzu.internal.golden-gryphon.com> (raw)
In-Reply-To: 479754D1.3000507@gnu.org
On Wed, 23 Jan 2008 09:53:05 -0500, Sam Steingold <sds@gnu.org> said:
> Richard Stallman wrote:
>> Would you like to volunteer to try one of the candidate bug trackers
>> using only email, and see how well it works?
> In my experience, "e-mail - operated bug trackers" (e.g., RT) are much
> worse than simple mailing lists. specifically, if you use more than
> one e-mail address (as I do), they turn into an unmitigated disaster
> because they tend to require that you reply using the same address
> which was used when you first submitted the issue &c.
This is certainly not a limitation of the Debian bug tracking
system, debbugs, since it does not require people to be "registered".
Having used this for almost a decade, I can say that in my personal
opinion, debbugs has outperformed any othe issue tracking system I have
used (I ahve run bugzilla and request tracker for my day job).
This is how it works:
http://www.debian.org/Bugs/server-control
Debbugs keeps track of which versions of the software various
issues are related to, and has a web front end for viewing. The web
frontend can be ordered by various ways; please see the difference
between:
http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=debian-policy&users=srivasta@debian.org&ordering=policy
and
http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=debian-policy
Same package, same bugs, but ordered in a totally different
fashion; and any user can set up their own classification and order,
independently of anyone else, and share the classification/order for
the bugs.
Also, people can track the same issue across different packages
individually without needing sysadmin intervention; hewre are bugs that
are deemed to be release critical and affect arm, m68k, s390, and sparc:
http://bugs.debian.org/cgi-bin/pkgreport.cgi?which=tag&users=debian-release@lists.debian.org&tag=rc-arm,rc-m68k,rc-s390,rc-sparc&nam0=Status&pri0=pending:pending,forwarded,pending-fixed,fixed,done&ttl0=Outstanding,Forwarded,Pending%20Upload,Fixed%20in%20NMU,Resolved&nam1=Architecture&pri1=tag:rc-arm,rc-m68k,rc-s390,rc-sparc&ttl1=arm,m68k,s390,sparc&ord1=0,1,2,3
Please do not think that debbugs is yet anotherrun of the mill
system with the flaws of other bug systems; it truly stands alone.
manoj
ps: here is a refcard for the system:
http://www.debian.org/Bugs/server-refcard
--
"Unemployment is an inconvenience." John F. Haugh II
Manoj Srivastava <srivasta@acm.org> <http://www.golden-gryphon.com/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
next prev parent reply other threads:[~2008-01-23 16:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-22 17:01 Moving to the new infrastructure Eric S. Raymond
2008-01-22 21:01 ` Karl Fogel
2008-01-23 9:30 ` Richard Stallman
2008-01-23 14:24 ` Karl Fogel
2008-01-23 14:53 ` Sam Steingold
2008-01-23 16:41 ` Manoj Srivastava [this message]
2008-01-23 17:49 ` Stephen J. Turnbull
2008-01-23 21:41 ` Richard Stallman
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=871w88lcjq.fsf@anzu.internal.golden-gryphon.com \
--to=srivasta@ieee.org \
--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).