[Dovecot] bugzilla or other similar bug tracking systems
I was wondering if it could be useful to use such tools to keep track of users bugs.
I find somehow harder to search the mailing list if a bug is known, if it's being worked on, if it needs more feedback, in witch release it has been eventually solved, and so on.
Any thoughts?
Regards, Diego.
On Aug 1, 2008, at 12:51 AM, Diego Liziero wrote:
I was wondering if it could be useful to use such tools to keep track of users bugs.
I find somehow harder to search the mailing list if a bug is known, if it's being worked on, if it needs more feedback, in witch release it has been eventually solved, and so on.
I'd like to have a bug tracking system that basically keeps track of
threads in this mailing list that have bugs and with some extra
metadata assigned to them about the bug states etc. But that'd require
- ANNOTATE extension for Dovecot and 2) Writing the bug tracking
system itself..
I don't really want to have a separate bug tracking system where I'd
be the only one handling the bug reports.
On Fri, Aug 1, 2008 at 1:12 AM, Timo Sirainen <tss@iki.fi> wrote:
On Aug 1, 2008, at 12:51 AM, Diego Liziero wrote:
I was wondering if it could be useful to use such tools to keep track
of users bugs.
I find somehow harder to search the mailing list if a bug is known, if it's being worked on, if it needs more feedback, in witch release it has been eventually solved, and so on.
I'd like to have a bug tracking system that basically keeps track of threads in this mailing list that have bugs and with some extra metadata assigned to them about the bug states etc. But that'd require 1) ANNOTATE extension for Dovecot and 2) Writing the bug tracking system itself..
I don't really want to have a separate bug tracking system where I'd be the only one handling the bug reports.
Ok, I'm waiting for that. My belief is that a public bug tracking system, whatever you choose, could bring more people into the bug fixing process.
Who knows, maybe during the summer holidays someone that would like to spend some weeks to help this project could find an easy way to start.
Timo Sirainen skrev:
I don't really want to have a separate bug tracking system where I'd be the only one handling the bug reports.
I know this is personal, but when I had my own company developing software, I was the only one handling bug requests. But nevertheless, I felt it was a good thing just to keep track of things, and to respond to vendors and customers "yes this is already being tracked in [the term actually was 'trouble report'] #1234". Sounded more professional and also made me ease a little on my personal memory load.
This was before Bugzilla was developed. Now, in my current job, we use Bugzilla.
I can really recommend Bugzilla, using priorities you always know what to do and when you're finished for release. In your case, paid development could always get prio 1 (highest).
Whether you want to make it publicly available is up to you.
/Peter
participants (3)
-
Diego Liziero
-
Peter Lindgren
-
Timo Sirainen