From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.90.79.9 with SMTP id c9cs61570agb; Tue, 3 Nov 2009 15:12:07 -0800 (PST) Received: by 10.224.51.205 with SMTP id e13mr328889qag.387.1257289926186; Tue, 03 Nov 2009 15:12:06 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 9si796035qyk.27.2009.11.03.15.12.05; Tue, 03 Nov 2009 15:12:06 -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; dkim=neutral (body hash did not verify) header.i=@gmail.com Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id C1FB31598096; Tue, 3 Nov 2009 18:12:05 -0500 (EST) Received: from mail-qy0-f174.google.com (mail-qy0-f174.google.com [209.85.221.174]) by rubyforge.org (Postfix) with ESMTP id 464061598031 for ; Tue, 3 Nov 2009 18:11:52 -0500 (EST) Received: by qyk4 with SMTP id 4so3167055qyk.33 for ; Tue, 03 Nov 2009 15:11:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:from:date:x-google-sender-auth:message-id:subject:to :content-type; bh=mEomyJ+e9tC7OTgPxMhuDxYVbwM/MXSHpbZKfAZpc50=; b=RUP46gc5Fyv/VDVsJiQSysg8a2yF5953/pe0cDqiSBhtWZ1g9D4NxQF3MeAImKwlnF tr7k5XDl9ewlMZZ8HjAn+iWzZesDjZsejCZPzhtAryV61WDHdbFZJgMlxpWwbNIUBjit 6eL3sB6PDi6a8bl9FSm7f5ZAeJPoG/K0lTlqg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type; b=sXaX3laNZ1Z42n6f217kxi1HlS//O0xq7VRWFBNIeq3eBLnkWbRIKrbtq1abUIf8+i BL9Sv/5d4tXCvoNVMsRoPNr3Qu5t5XjZ4TrHgDuwVhJQQwUsOKdQool23M4Yp+HXm1Cs rdd8P73+XPfUvecAV+j6TI2cJMQVBPSMtqdI0= MIME-Version: 1.0 Received: by 10.229.119.154 with SMTP id z26mr95876qcq.38.1257289911125; Tue, 03 Nov 2009 15:11:51 -0800 (PST) In-Reply-To: <1257111816-sup-4397@peray> References: <1257111816-sup-4397@peray> From: Jim Cheetham Date: Wed, 4 Nov 2009 12:11:31 +1300 X-Google-Sender-Auth: 29cfe947434f2b1f Message-ID: To: sup-talk 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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, Nov 2, 2009 at 10:52 AM, Nicolas Pouillard 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. -jim _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk