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-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Swz1h-0001kb-VO for bitcoin-development@lists.sourceforge.net; Thu, 02 Aug 2012 17:17:33 +0000 X-ACL-Warn: Received: from zinan.dashjr.org ([173.242.112.54]) by sog-mx-4.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1Swz1h-0003HY-1Z for bitcoin-development@lists.sourceforge.net; Thu, 02 Aug 2012 17:17:33 +0000 Received: from ishibashi.localnet (unknown [97.96.85.141]) (Authenticated sender: luke-jr) by zinan.dashjr.org (Postfix) with ESMTPSA id 1FD8C56055A; Thu, 2 Aug 2012 17:17:29 +0000 (UTC) From: "Luke-Jr" To: bitcoin-development@lists.sourceforge.net Date: Thu, 2 Aug 2012 17:17:14 +0000 User-Agent: KMail/1.13.7 (Linux/3.4.4-gentoo-nestfix; KDE/4.8.3; x86_64; ; ) References: In-Reply-To: X-PGP-Key-Fingerprint: E463 A93F 5F31 17EE DE6C 7316 BD02 9424 21F4 889F X-PGP-Key-ID: BD02942421F4889F X-PGP-Keyserver: hkp://pgp.mit.edu MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201208021717.15759.luke@dashjr.org> X-Spam-Score: -0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain X-Headers-End: 1Swz1h-0003HY-1Z Subject: Re: [Bitcoin-development] Version 0.7 release planning 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, 02 Aug 2012 17:17:34 -0000 On Thursday, August 02, 2012 4:43:25 PM Jeff Garzik wrote: > Opening the floor... What do we collectively want to happen, before > 0.7 release? What is the todo list for 0.7? Based on pull-capable dev comments, I've personally noted these branches as accepted for 0.7: > 7) HOPEFULLY: Addnode optimization and addnode access via RPC > BlueMatt https://github.com/bitcoin/bitcoin/pull/1549 > > 8) MAYBE: Transition to requiring block height in block coinbases > gavinandresen https://github.com/bitcoin/bitcoin/pull/1526 > > 10) I THINK WE WANT THIS? Make IPv6 support optional again (defaults > to enabled) > luke-jr https://github.com/bitcoin/bitcoin/pull/1431 > > 11) MAYBE: getblocktemplate ('getmemorypool', post IRC debate) > luke-jr https://github.com/bitcoin/bitcoin/pull/936 + + m) getmemorypool: longpolling support + luke-jr https://github.com/bitcoin/bitcoin/pull/1355 + + m) Refactor transaction/accounting time + luke-jr https://github.com/bitcoin/bitcoin/pull/1393 I also personally feel these are appropriate and ready for 0.7: > 4) Add 'mempool' P2P command, and extend 'getdata' behavior > jgarzik https://github.com/bitcoin/bitcoin/pull/1641 > > 6) JSON-RPC method: prioritisetransaction > luke-jr https://github.com/bitcoin/bitcoin/pull/1583 > > 9) RPC: add facility to enable RPCs to run outside cs_main, wallet locks > jgarzik https://github.com/bitcoin/bitcoin/pull/1493 + + m) Treat generation (mined) transactions less different from receive + transactions + luke-jr https://github.com/bitcoin/bitcoin/pull/1409 Also these, but they need testing: > 1) CreateNewBlock: Child-pays-for-parent / Add transaction fee later > luke-jr https://github.com/bitcoin/bitcoin/pull/1647 > > 5) PROBABLY NOT, BUT MAYBE: Relay blocks as a "preview" before > checking the transactions in them > luke-jr https://github.com/bitcoin/bitcoin/pull/1586 + + m) Bitcoin-Qt (Windows only): enable DEP for bitcoin-qt.exe + diapolo https://github.com/bitcoin/bitcoin/pull/1614 I also feel it is very important that Wumpus/laanwj decide on a name for his client (formerly known as Bitcoin-Qt) and add it to the software instead of simply claiming it is "Bitcoin" as it has for a week or so now - that change is anticompetitive and will confuse new users into thinking Bitcoin is the software too easily. Luke