Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1TWRpc-0005Nb-5v for bitcoin-development@lists.sourceforge.net; Thu, 08 Nov 2012 13:07:40 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.210.175 as permitted sender) client-ip=209.85.210.175; envelope-from=gmaxwell@gmail.com; helo=mail-ia0-f175.google.com; Received: from mail-ia0-f175.google.com ([209.85.210.175]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1TWRpY-00020W-IF for bitcoin-development@lists.sourceforge.net; Thu, 08 Nov 2012 13:07:40 +0000 Received: by mail-ia0-f175.google.com with SMTP id b35so1983071iac.34 for ; Thu, 08 Nov 2012 05:07:31 -0800 (PST) MIME-Version: 1.0 Received: by 10.43.97.8 with SMTP id ci8mr7021357icc.28.1352380051346; Thu, 08 Nov 2012 05:07:31 -0800 (PST) Received: by 10.64.171.73 with HTTP; Thu, 8 Nov 2012 05:07:31 -0800 (PST) In-Reply-To: References: Date: Thu, 8 Nov 2012 08:07:31 -0500 Message-ID: From: Gregory Maxwell To: Mike Hearn Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Score: -1.6 (-) 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 (gmaxwell[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 X-Headers-End: 1TWRpY-00020W-IF Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] IRC meeting agenda, 18:00 UTC Thursday 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: Thu, 08 Nov 2012 13:07:40 -0000 On Thu, Nov 8, 2012 at 4:19 AM, Mike Hearn 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 Bitc= oin I agree on getting the bloom filtering stuff in for 0.8, though I don't think it'll need any marketing at all=E2=80=94 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.