Not logged in
Log in now
Create an account
Subscribe to LWN
LWN.net Weekly Edition for December 5, 2013
Deadline scheduling: coming soon?
LWN.net Weekly Edition for November 27, 2013
ACPI for ARM?
LWN.net Weekly Edition for November 21, 2013
A while ago I was thinking about a bug tracking system for Dovecot which was mainly based on
mailing list archives. I'm still not using a BTS, so maybe some day I'll actually get it
implemented. http://www.dovecot.org/list/dovecot/2007-January/018786.html explains it a bit.
Posted Nov 24, 2007 20:21 UTC (Sat) by i3839 (guest, #31386)
I'm not sure, but it looks like overkill. Too complicated for what you really want I think.
Adding a bug number is useless, because the number doesn't add any information. Can as wel
just use the subject line.
Priority is as far as I can judge rarely used in any way constructive way in reality. At best
it's the order in which the bugs will be fixed by the dev, but that can be a private list too.
Same for status. What else is needed other than "[BUG] Bla broken [FIXED]"? The bug is open
until FIXED shows up in the subject line, it's being investigated when people reply to it, and
being handled when a dev replied to it.
Devs probably want to keep all kind of info in notes for bugs, but no need to stuff such kind
of info into IMAP annotations.
So I think that just parsing the subject lines for certain keywords is plenty. Perhaps
comparing senders with a list of devs to know what the person's role is too, but not much
Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds