[Dovecot] Bugtracking system
udo.rader at bestsolution.at
Tue Dec 6 23:20:03 EET 2005
Am Dienstag, den 06.12.2005, 15:46 -0500 schrieb Glenn Leavell:
> On Tue, Dec 06, 2005 at 12:34:56PM -0800, Dan Hollis wrote:
> > On Tue, 6 Dec 2005, Glenn Leavell wrote:
> > >On Tue, Dec 06, 2005 at 08:09:09PM +0200, Timo Sirainen wrote:
> > >>On Fri, 2005-12-02 at 10:57 -0500, Glenn Leavell wrote:
> > >>>Back in April, there was a little discussion about the possibility of
> > >>>using
> > >>>a bug tracking system for Dovecot (Bugzilla, Trac, and Mantis were
> > >>>mentioned). Do you think it might be time to revisit that?
> > >>Still would be a good idea. Hmm. Last I tried, Trac didn't want to get
> > >>installed without SVN. Mantis requires MySQL and I'd rather avoid that.
> > >>So, would it be Bugzilla then? It seems to nowadays support PostgreSQL
> > >>and it's kind of a standard everywhere. :)
> > >If that's what you're comfortable with, then that sounds great to me. I
> > >know that a lot of us are certainly experienced with *using* it.
> > Please, no bugzilla. It's top-heavy and really cumbersome to use.
> > Mantis has a much better interface, and is much more straightforward to
> > configure and use. Please save the database elitism for the
> > linux-vs-freebsd and atari-vs-commodore flame lists where those
> > discussions belong.
> > I've used and setup a _lot_ of different bugtrackers extensively and
> > mantis sucks the least. And I have used some which _really_ suck.
> I agree that Bugzilla can be cumbersome. But I'm most interested in there
> being *some* bug tracking system in place. If Timo is going to be managing
> the system, his preference will probably carry the most weight. That being
> said, it sounds like you've got a lot of experience in this area, and
> perhaps Timo would be wise to listen! After all, Dovecot is a great
> product, so we'll probably be using whatever system gets put in place for a
> long time to come.
You are absolutely right. Introducing a bugtracker is always a major
decision and should be well considered (and I am glad that there is only
one person in charge :-)
On point against trac (though it looks very nice and seems to be the
"one tool for everything") is that it _is_ a tool for everything
(integrated wiki, documentation manager, ...). It can complicate things
a lot if the "everything" fails or breaks for whatever reason.
One of the major reasons why some time ago we chose not to use trac was
the fact that it lacks finegrained access controls on bugs. Just go to
the trac homepage, open the "issues" or "tickets" page and edit any bug
you like (close it, fix it, whatever). If you have the right to add a
comment on some bug, it implicitly means that you can also close/fix/...
Well, as you see, I have some "issues" with trac ;-)
BestSolution.at EDV Systemhaus GmbH
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
Url : http://dovecot.org/pipermail/dovecot/attachments/20051206/51b00375/attachment.pgp
More information about the dovecot