From: Gregory Maxwell <gmaxwell@gmail•com>
To: Mike Hearn <mike@plan99•net>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] IRC meeting agenda, 18:00 UTC Thursday
Date: Thu, 8 Nov 2012 08:07:31 -0500 [thread overview]
Message-ID: <CAAS2fgQkKbLXAYDUfwmKumNKdfyT08EJZgHX9qm-VBt36inz6g@mail.gmail.com> (raw)
In-Reply-To: <CANEZrP0LUv69wYwg_6ivPc=mFiGEYKomaJXmmT2Zm14bKik0bQ@mail.gmail.com>
On Thu, Nov 8, 2012 at 4:19 AM, Mike Hearn <mike@plan99•net> wrote:
> Is it time to feature-freeze 0.8
>
> I'd like more time to get the bloom filtering work in. It'll be easier to
> promote the 0.8 release if we can sell it as "important
> scalability/performance improvement for the network, upgrade to help Bitcoin
I agree on getting the bloom filtering stuff in for 0.8, though I
don't think it'll need any marketing at all— ultraprune speaks for
itself. :P
I'm also concerned about overselling it for miners and merchants when
the ultraprune stuff is such a major change.
Since the current changes will just need a lot of testing and soaking
time which is pretty much independent of RPC and GUI changes it might
be unfortunate to feature freeze those things and then have a long
delay just on QA for the other stuff. I do think we need to talk
about what we think we need to o to get what we have now ready for
release.
next prev parent reply other threads:[~2012-11-08 13:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-06 18:47 Gavin Andresen
2012-11-06 19:13 ` Luke-Jr
2012-11-06 19:56 ` slush
2012-11-06 22:12 ` Luke-Jr
2012-11-07 19:37 ` Pieter Wuille
2012-11-08 9:19 ` Mike Hearn
2012-11-08 12:56 ` Pieter Wuille
2012-11-08 13:07 ` Gregory Maxwell [this message]
[not found] ` <CA+s+GJDVLLv8troMfeyWoOwM3EH4GHYtd=bzUgmg_ZegVT6kXw@mail.gmail.com>
2012-11-08 13:10 ` [Bitcoin-development] Fwd: " Wladimir
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=CAAS2fgQkKbLXAYDUfwmKumNKdfyT08EJZgHX9qm-VBt36inz6g@mail.gmail.com \
--to=gmaxwell@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=mike@plan99$(echo .)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