From: Wladimir <laanwj@gmail.com>
To: steve <steve@mistfpga.net>
Cc: Bitcoin Development List
<bitcoin-development@lists.sourceforge.net>,
Bill Hees <billhees@gmail.com>
Subject: Re: [Bitcoin-development] Bitcoin Testing Project
Date: Wed, 26 Sep 2012 14:49:21 +0200 [thread overview]
Message-ID: <CA+s+GJBM4DwDoqT8RC0+SyrLYrLGZuGZSuoj7zbHunQa3kFoRA@mail.gmail.com> (raw)
In-Reply-To: <5062F4F8.6040504@mistfpga.net>
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
next prev parent reply other threads:[~2012-09-26 12:49 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-25 18:32 [Bitcoin-development] Bitcoin Testing Project steve
2012-09-25 20:41 ` Matt Corallo
2012-09-26 5:49 ` Wladimir
2012-09-26 11:41 ` Daniel F
2012-09-26 12:00 ` Luke-Jr
2012-09-26 12:28 ` steve
2012-09-26 12:49 ` Wladimir [this message]
2012-09-26 13:22 ` steve
2012-09-26 16:06 ` Mark Friedenbach
2012-09-26 17:10 ` Jeff Garzik
2012-09-26 17:44 ` steve
2012-09-26 18:09 ` Gavin Andresen
2012-09-29 18:26 ` steve
2012-10-01 13:52 ` Arklan Uth Oslin
2012-10-01 14:28 ` steve
2012-10-01 16:52 ` Peter Vessenes
2012-10-03 1:15 ` steve
2012-10-03 2:02 ` Gregory Maxwell
2012-10-03 3:00 ` steve
[not found] ` <CAMGNxUu=LTZyAxKt3pAYSVxyhHBU9pyJPCiFs-tA_weYNNXbtw@mail.gmail.com>
[not found] ` <CAMGNxUuHRBkE_MbmY=A0vQvq=gMfzCFG8Us7SdBn-14KiKMaNg@mail.gmail.com>
2012-10-03 5:04 ` Peter Vessenes
2012-10-03 16:06 ` steve
2012-10-03 16:11 ` Arklan Uth Oslin
2012-10-03 16:15 ` [Bitcoin-development] Fwd: " steve
2012-10-03 17:09 ` Peter Vessenes
2012-10-03 17:30 ` Gavin Andresen
2012-09-27 0:53 ` [Bitcoin-development] " Matt Corallo
2012-09-27 2:29 ` Gregory Maxwell
2012-09-25 20:49 ` Daniel F
2012-09-25 21:25 ` Gary Rowe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+s+GJBM4DwDoqT8RC0+SyrLYrLGZuGZSuoj7zbHunQa3kFoRA@mail.gmail.com \
--to=laanwj@gmail.com \
--cc=billhees@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=steve@mistfpga.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox