From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.90.79.9 with SMTP id c9cs16180agb; Sat, 7 Nov 2009 03:16:06 -0800 (PST) Received: by 10.224.14.143 with SMTP id g15mr2984205qaa.123.1257592565848; Sat, 07 Nov 2009 03:16:05 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 7si1126154qyk.80.2009.11.07.03.16.05; Sat, 07 Nov 2009 03:16:05 -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 117731598079; Sat, 7 Nov 2009 06:16:05 -0500 (EST) Received: from kuovi.tilus.net (kuovi.tilus.net [80.68.89.168]) by rubyforge.org (Postfix) with ESMTP id E4AA418582AC for ; Sat, 7 Nov 2009 06:15:56 -0500 (EST) Received: by kuovi.tilus.net (Postfix, from userid 1000) id 083596012; Sat, 7 Nov 2009 11:15:56 +0000 (GMT) From: Tero Tilus To: sup-talk In-reply-to: <1257524700-sup-9112@masanjin.net> References: <1257524700-sup-9112@masanjin.net> Date: Sat, 07 Nov 2009 13:15:56 +0200 Message-Id: <1257591624-sup-8158@tilus.net> User-Agent: Sup/git Subject: Re: [sup-talk] sup bug tracker 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 William Morgan, 2009-11-06 18:33: > If you have existing bug reports or feature requests and you don't > want to rely on my faulty memory any more, feel free to resubmit > them here. What should be the policy with issues are reported/discussed on irc or mailinglist but are not reported to tracker? Should The Sup Issues Task Force(TM) ;) report them to tracker or try to push the original reporter to do it? Should we (The SITF) skim mailinglist archives and transfer reported unfixed bugs (with links to archives) to tracker? > I'm going to point the 0.9.1 crash message there too. Sup home http://sup.rubyforge.org/ is not yet pointing there. -- Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/ _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk