Re: [sup-talk] Choosing a bug tracker for Sup

From: Mike Kelly <pioto@pioto.org>
To: sup-talk@rubyforge.org
Subject: Re: [sup-talk] Choosing a bug tracker for Sup
Date: Tue, 3 Nov 2009 19:07:24 -0500	[thread overview]
Message-ID: <20091103190724.1dd5d891@aether.home.pioto.org> (raw)
In-Reply-To: <f4cc59760911031511m7f99a4bck4d9b31f4aa7704e2@mail.gmail.com>

On Wed, 4 Nov 2009 12:11:31 +1300
Jim Cheetham <jim@gonzul.net> wrote:

> On Mon, Nov 2, 2009 at 10:52 AM, Nicolas Pouillard
> <nicolas.pouillard@gmail.com> wrote:
> > I would like to discuss more the issue of choosing a bug tracker
> > for sup.
> 
> Having had a quick read of this thread, I think that trac
> (http://trac.edgewall.com) would meet your goals.
> 
> It's a simple single-project combination of wiki, ticketing engine and
> repository browser. Tickets can be received by email, ticket updates
> can be emailed to a set of interested subscribers, and checkins to the
> repository can close tickets (via simple hooks). The wiki markup
> provides simple access to changes, tickets & files.

Trac doesn't really allow you to reply to tickets by email. At least,
not with any plugin that I've used.

Also, I've used trac for years for another project, and I wouldn't
recommend it. (It's been a memory hog, among other things).

-- 
Mike Kelly
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk