From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.90.117.16 with SMTP id p16cs408477agc; Sun, 1 Nov 2009 06:45:22 -0800 (PST) Received: by 10.224.36.142 with SMTP id t14mr2250690qad.17.1257086720416; Sun, 01 Nov 2009 06:45:20 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 31si6337275qyk.87.2009.11.01.06.45.20; Sun, 01 Nov 2009 06:45:20 -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 173B51858249; Sun, 1 Nov 2009 09:45:20 -0500 (EST) Received: from entry.masanjin.net (masanjin.net [209.20.72.13]) by rubyforge.org (Postfix) with ESMTP id 3871C1858291 for ; Sun, 1 Nov 2009 09:39:26 -0500 (EST) Received: from w by entry.masanjin.net with local (Exim 4.69) (envelope-from ) id 1N4baX-0003CQ-85 for sup-talk@rubyforge.org; Sun, 01 Nov 2009 06:39:25 -0800 From: William Morgan To: sup-talk In-reply-to: <1256987483-sup-338@tilus.net> References: <1256749942-sup-4831@arrakis.es.net> <1256760295-sup-9873@peray> <1256760970-sup-8118@arrakis.es.net> <1256939476-sup-2864@masanjin.net> <1256987483-sup-338@tilus.net> Date: Sun, 01 Nov 2009 06:39:25 -0800 Message-Id: <1257086191-sup-1136@masanjin.net> User-Agent: Sup/git Subject: Re: [sup-talk] [PATCH] minor nits in exception apology message 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: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org Reformatted excerpts from Tero Tilus's message of 2009-10-31: > How about setting up a loose team which would handle the incoming bug > reports (for you), track/sort all of them and fix what they feel like > fixing and maybe upon request/occasionally report somewhere the > current status (how many minors and majors open). As far as I'm concerned, that would be great. I'm open to suggestions about how to organize this. At this point I'm pretty convinced I will never actually like a bug tracker, and I don't have the energy to write another one, so for someone else to take the initiative would be awesome. -- William _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk