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

From: Reid Thompson <reid.thompson@ateb.com>
To: Mike Kelly <pioto@pioto.org>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Choosing a bug tracker for Sup
Date: Tue, 3 Nov 2009 11:49:53 -0500	[thread overview]
Message-ID: <20091103164953.GA20359@ateb.com> (raw)
In-Reply-To: <afd0a1d89ddee05080dcaf20f03bdefa@localhost>

On Tue, Nov 03, 2009 at 10:34:24AM -0500, Mike Kelly wrote:
> 
> On Tue, 03 Nov 2009 07:16:15 -0800, William Morgan
> <wmorgan-sup@masanjin.net> wrote:
> > Reformatted excerpts from Mike Kelly's message of 2009-11-03:
> >> As much as I hate to suggest it... RT should have all of these
> >> qualities.
> > 
> > Rrrrrrrrreally. Is it a pain to set up? Why do you hate to suggest it?
> > (I've heard people complain about it before, but I don't remember any of
> > the details.)
> 
> Yes, somewhat, IIRC. But, I haven't really ever had to set it up. It's one
> of those things which requires half of CPAN to work. So, it was annoying
> when I made an attempt to package it for a distro, but if you're just
> installing it following their directions, it's probably not that bad.
> 
> But, someone is able to get away with charging $3250 a month for a
> "platinum" managed install of it. (Then again, some enterprises will pay
> anything for hosting...)
> 
> Let me try a test install real quick, and I'll get back to you.

I just started looking at it, so not sure if it fits all needs but
fossil has a built in bugtracker

http://www.fossil-scm.org/index.html/doc/tip/www/index.wiki


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