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

From: Sebastian Schwarz <seschwar@googlemail.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Choosing a bug tracker for Sup
Date: Tue, 3 Nov 2009 17:20:47 +0100	[thread overview]
Message-ID: <20091103162047.GD2963@pineapple.q.wohnheim-jahnplatz.de> (raw)
In-Reply-To: <1257261315-sup-977@masanjin.net>

On 2009-11-03 at 07:16 -0800, William Morgan wrote:
> Is it a pain to set up?

I have never installed, administered or used RT before, but curiously
digging around its homepage I found this:

http://bestpractical.com/rt/features.html praises it as "Easy to
install".  However on http://wiki.bestpractical.com/view/HomePage
it says:

> RT doesn't come with a formal, formatted users or administrators
> guide, but it's likely most of what you need to know to use and run it
> is contained somewhere within this wiki, so look around a little, be
> patient... and try not to install RT on a Sunday night when you need
> to run it in production on Monday: it's big, and learning how to set
> it up can take some time.

Can anyone with more experience with RT comment on this?

Moreover I'd like to advertise/suggest [Roundup][1].  Apart form a slim
web interface -- [here][2] Python's issue tracker as an example -- it
also offers a fully functional [email interface][3], which allows --
from what I understand -- creating, discussing and setting properties
like status and labels of issues.

As a note on the ease of installation: Roundup's [documentation on
installation][4] begins with: "Set aside 15-30 minutes."  But again
I have no personal experience to back this claim up.  Can anyone
comment on this or Roundup in general?

[1]: http://roundup.sourceforge.net/
[2]: http://bugs.python.org/
[3]: http://roundup.sourceforge.net/docs/user_guide.html#e-mail-gateway
[4]: http://www.roundup-tracker.org/docs/installation.html#installation
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk