From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: gnus bugs tracking
Date: Sat, 22 Mar 2003 17:05:34 +0100 [thread overview]
Message-ID: <ilubs03xu7l.fsf@latte.josefsson.org> (raw)
In-Reply-To: <87r88zpp2d.fsf@pale.sj.ru> (Alexander Kotelnikov's message of "Sat, 22 Mar 2003 15:23:54 +0300")
Alexander Kotelnikov <sacha@myxomop.com> writes:
> Hi.
>
> Sometimes bugs reported to ding@gnus.org are forgotten without a fix.
> It's a pity. And it is a trouble, since gnus does not have its own bug
> tracking system.
>
> Any comments?
Adding meta-data management to the current gnus.gnus-bug is one useful
improvement I can see. Like, e.g., making it possible to enter the
summary buffer and list all "open" bugs, and be able to "close" them
somehow. I'm not sure how to best implement this though. With IMAP
it would have been simple, by using "gnus-bug-open", "gnus-bug-fixed",
"gnus-bug-wontfix" etc flags on the messages.
Web based bug tracker systems are just a time sink. The bugs are
tracked, but less frequently fixed because developers cannot
prioritize. In mail, if a problem is serious many people will report
it many times until it is fixed. So it has a built-in flexible
adaptive priority system which most web BTS's lack.
next prev parent reply other threads:[~2003-03-22 16:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-22 12:23 Alexander Kotelnikov
2003-03-22 12:42 ` Vasily Korytov
2003-03-22 13:14 ` Alexander Kotelnikov
2003-03-22 13:26 ` Frank Schmitt
2003-03-22 16:05 ` Simon Josefsson [this message]
2003-03-22 17:49 ` Frank Schmitt
2003-03-22 18:06 ` Alex Schroeder
2003-03-23 23:57 ` Alexander Kotelnikov
2003-03-26 12:18 ` Alexander Kotelnikov
2003-03-30 2:57 ` Lars Magne Ingebrigtsen
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=ilubs03xu7l.fsf@latte.josefsson.org \
--to=jas@extundo.com \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).