From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1TGr3U-0006BV-C4 for bitcoin-development@lists.sourceforge.net; Wed, 26 Sep 2012 12:49:32 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.217.175 as permitted sender) client-ip=209.85.217.175; envelope-from=laanwj@gmail.com; helo=mail-lb0-f175.google.com; Received: from mail-lb0-f175.google.com ([209.85.217.175]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1TGr3Q-0001pU-Mv for bitcoin-development@lists.sourceforge.net; Wed, 26 Sep 2012 12:49:32 +0000 Received: by lbky2 with SMTP id y2so1648826lbk.34 for ; Wed, 26 Sep 2012 05:49:22 -0700 (PDT) MIME-Version: 1.0 Received: by 10.112.26.196 with SMTP id n4mr305539lbg.129.1348663762165; Wed, 26 Sep 2012 05:49:22 -0700 (PDT) Received: by 10.112.47.231 with HTTP; Wed, 26 Sep 2012 05:49:21 -0700 (PDT) In-Reply-To: <5062F4F8.6040504@mistfpga.net> References: <5061F8CC.9070906@mistfpga.net> <1348605677.2284.2.camel@localhost.localdomain> <5062F4F8.6040504@mistfpga.net> Date: Wed, 26 Sep 2012 14:49:21 +0200 Message-ID: From: Wladimir To: steve Content-Type: text/plain; charset=UTF-8 X-Spam-Score: -1.4 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (laanwj[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature 0.2 AWL AWL: From: address is in the auto white-list X-Headers-End: 1TGr3Q-0001pU-Mv Cc: Bitcoin Development List , Bill Hees Subject: Re: [Bitcoin-development] Bitcoin Testing Project X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Sep 2012 12:49:32 -0000 Steve, > So, currently there are 4 potential places for bugs to be reported > 1 - jenkins (and unit tests) > 2 - git > 3 - mailing list > 4 - forum (bitcointalk...) > 5? - is there still the ability to add bugs via sourceforge? Currently github is the authoritative place to report issues. When someone reports a bug on the mailing list, IRC or forum, they are generally asked to make a github issue (or, someone else makes the issue for them). Failed tests are generally also reported on github, by the pull tester. We currently have 232 issues, mostly classified into categories such as "Bug", "Improvement", "GUI", "Wallet", and so on. Also it's easy to refer to github issues in commits with #123, with automatic linking. I'm not sure it is worth the effort to move to another system (especially if you need a another login etc...). But I'm probably misunderstanding what you're trying to do. Wladimir