From mboxrd@z Thu Jan  1 00:00:00 1970
Received: by 10.90.79.9 with SMTP id c9cs25522agb;
        Tue, 3 Nov 2009 06:52:15 -0800 (PST)
Received: by 10.224.114.149 with SMTP id e21mr38865qaq.215.1257259934565;
        Tue, 03 Nov 2009 06:52:14 -0800 (PST)
Return-Path: <sup-talk-bounces@rubyforge.org>
Received: from rubyforge.org (rubyforge.org [205.234.109.19])
        by mx.google.com with ESMTP id 11si173174qyk.112.2009.11.03.06.52.14;
        Tue, 03 Nov 2009 06:52:14 -0800 (PST)
Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19;
Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org
Received: from rubyforge.org (rubyforge.org [127.0.0.1])
	by rubyforge.org (Postfix) with ESMTP id 3D89B3C805A;
	Tue,  3 Nov 2009 09:52:14 -0500 (EST)
Received: from everglades.pioto.org (everglades.pioto.org [207.192.69.249])
	by rubyforge.org (Postfix) with ESMTP id 6D4BB15B8025
	for <sup-talk@rubyforge.org>; Tue,  3 Nov 2009 09:50:56 -0500 (EST)
Received: by everglades.pioto.org (Postfix, from userid 81)
	id 908281602FE; Tue,  3 Nov 2009 09:50:55 -0500 (EST)
To: sup-talk <sup-talk@rubyforge.org>
MIME-Version: 1.0
Date: Tue, 03 Nov 2009 09:50:55 -0500
From: Mike Kelly <pioto@pioto.org>
In-Reply-To: <1257169654-sup-6224@masanjin.net>
References: <1257111816-sup-4397@peray> <1257169654-sup-6224@masanjin.net>
Message-ID: <02055f053011496a2dcb9085b7e7535f@localhost>
X-Sender: pioto@pioto.org
User-Agent: RoundCube Webmail/0.3-stable
Subject: Re: [sup-talk] Choosing a bug tracker for Sup
X-BeenThere: sup-talk@rubyforge.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: User & developer discussion of Sup <sup-talk.rubyforge.org>
List-Unsubscribe: <http://rubyforge.org/mailman/options/sup-talk>,
	<mailto:sup-talk-request@rubyforge.org?subject=unsubscribe>
List-Archive: <http://rubyforge.org/pipermail/sup-talk>
List-Post: <mailto:sup-talk@rubyforge.org>
List-Help: <mailto:sup-talk-request@rubyforge.org?subject=help>
List-Subscribe: <http://rubyforge.org/mailman/listinfo/sup-talk>,
	<mailto:sup-talk-request@rubyforge.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sup-talk-bounces@rubyforge.org
Errors-To: sup-talk-bounces@rubyforge.org


On Mon, 02 Nov 2009 06:50:08 -0800, William Morgan
<wmorgan-sup@masanjin.net> wrote:
> Nice writeup. Just brainstorming, here are the features I personally
> find vital for an issue tracker that would make me happy:
> 
> 1. Web submission. 
> 
> 2. Developer discussion via email.
> 
> 3. Canonicality.
> 
> 4. Browseability.
> 
> I want a simple one. I can remember JIRA-style "ABC-123" names and
> that's really handy sometimes.

As much as I hate to suggest it... RT[1] should have all of these
qualities. It's used by CPAN, among other things. And, a sample ticket of
mine[2].

[1] http://bestpractical.com/rt
[2] https://rt.cpan.org/Public/Bug/Display.html?id=45040

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