From: John Smith <witchspace81@gmail•com>
To: Alex Waters <ampedal@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin-qt ready for merging
Date: Sun, 11 Sep 2011 09:54:18 +0000 [thread overview]
Message-ID: <CAJNQ0svPNAZSRBm+O88p4Spw6MmQinuT_S15Z56jb3Z6VAorwQ@mail.gmail.com> (raw)
In-Reply-To: <CAL0fb62M9=vKM4kag9rdQ=1bAbKdnoXD+7XR3eyKWY_Q4WEZXA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1522 bytes --]
Alex,
On Sun, Sep 11, 2011 at 7:45 AM, Alex Waters <ampedal@gmail•com> wrote:
> Hey John,
>
> It could be as simple as listing some things that you think could possibly
> break if qt is implemented. For example, "check the UI for artifacts". I
> don't really know what could potentially need to be tested, so any help
> would get things processed faster.
>
> I can't acknowledge a pull unless there is substantial evidence that it's
> been tested, especially something of this size...
>
It has been under development for a long time, the thread on the bitcointalk
forum is "substantial evidence" that many people are using it (also, I
receive quite a lot of mail about it, and the number of followers on github
steadily fluctuates around ~30). So nothing obvious is broken, at least, I
think has worked better than the Wx UI for quite a while.
But as I've said before I'm fine with keeping bitcoin-qt as a parallel,
experimental, release for a while. I think that's the only way to get more
testing with people that don't want to or can't build from source (could
just mark the download as "New GUI, experimental" or so...).
To be honest I think it should be merged at least as experimental ASAP, it
would save a lot of GUI complaints on the forum about things I've
implemented months ago already. However I will only put up a pull request as
soon as it is clear that it will actually be integrated. It is too much work
for me to keep the pull request up-to-date if it lingers for months like
many others have.
JS
[-- Attachment #2: Type: text/html, Size: 1894 bytes --]
next prev parent reply other threads:[~2011-09-11 9:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-11 0:20 Alex Waters
2011-09-11 7:37 ` John Smith
[not found] ` <CAL0fb62M9=vKM4kag9rdQ=1bAbKdnoXD+7XR3eyKWY_Q4WEZXA@mail.gmail.com>
2011-09-11 9:54 ` John Smith [this message]
2011-09-11 17:12 ` Gavin Andresen
-- strict thread matches above, loose matches on Subject: below --
2011-08-31 14:20 John Smith
2011-08-31 15:07 ` Matt Corallo
2011-09-01 2:11 ` John Smith
2011-09-01 2:13 ` Luke-Jr
2011-09-01 2:32 ` John Smith
2011-09-22 20:11 ` Luke-Jr
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=CAJNQ0svPNAZSRBm+O88p4Spw6MmQinuT_S15Z56jb3Z6VAorwQ@mail.gmail.com \
--to=witchspace81@gmail$(echo .)com \
--cc=ampedal@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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