From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.90.79.9 with SMTP id c9cs31513agb; Sat, 7 Nov 2009 08:32:25 -0800 (PST) Received: by 10.224.43.138 with SMTP id w10mr3104618qae.197.1257611545188; Sat, 07 Nov 2009 08:32:25 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 37si1412984qyk.122.2009.11.07.08.32.25; Sat, 07 Nov 2009 08:32:25 -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 DBD0E1D7886D; Sat, 7 Nov 2009 11:32:24 -0500 (EST) Received: from entry.masanjin.net (masanjin.net [209.20.72.13]) by rubyforge.org (Postfix) with ESMTP id 8FD1B1588065 for ; Sat, 7 Nov 2009 11:32:09 -0500 (EST) Received: from w by entry.masanjin.net with local (Exim 4.69) (envelope-from ) id 1N6oCu-0001IB-70 for sup-talk@rubyforge.org; Sat, 07 Nov 2009 08:32:08 -0800 From: William Morgan To: sup-talk In-reply-to: <1257591624-sup-8158@tilus.net> References: <1257524700-sup-9112@masanjin.net> <1257591624-sup-8158@tilus.net> Date: Sat, 07 Nov 2009 08:32:08 -0800 Message-Id: <1257610340-sup-9345@masanjin.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 Reformatted excerpts from Tero Tilus's message of 2009-11-07: > 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? I would like all new issues to go on the tracker, and I think it's completely reasonable to tell people who report things to the mailing list or IRC to instead use the issue tracker instead. > Should we (The SITF) skim mailinglist archives and transfer reported > unfixed bugs (with links to archives) to tracker? If the SITF wants to creating issues for existing bug reports, that would be very helpful. But please don't do it to the point that you get sick of it. > Sup home http://sup.rubyforge.org/ is not yet pointing there. Fixed, thanks! -- William _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk