1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
|
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 <jgarzik@exmulti.com>) id 1SwyUm-0000Cf-JO
for bitcoin-development@lists.sourceforge.net;
Thu, 02 Aug 2012 16:43:32 +0000
X-ACL-Warn:
Received: from mail-qc0-f175.google.com ([209.85.216.175])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1SwyUl-00083B-IX
for bitcoin-development@lists.sourceforge.net;
Thu, 02 Aug 2012 16:43:32 +0000
Received: by qcad10 with SMTP id d10so5662914qca.34
for <bitcoin-development@lists.sourceforge.net>;
Thu, 02 Aug 2012 09:43:26 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=google.com; s=20120113;
h=mime-version:x-originating-ip:date:message-id:subject:from:to
:content-type:x-gm-message-state;
bh=22pnxU2JjdE5Ne2VtoyHyo12CfzlmPv9wGlNs1KdxgU=;
b=Vt5XlOleHtLFRVHCXgtakuRjE+/JKHIKSnBrxHgwMdZTex4ZHw16Fh+a2ZgF11tFvP
aUJjCq4W45VX9woN0Qux4w/8JuosqQWKKDsGnc3Pt5csb0bSUAHjtO6nS5fcpZWtXGE/
YDZzyuQwkeIlFngd8UD0RLYznVXo19ui2NaHCU0FMqQMyrws8UojobQwq9y6RvK+EhKM
bOM8Ymu/44iT0VeD7HufNG47tEPUjeBxDxzTLWNL4Hib77ee4qc0Cufa7EjwIVMyG5nE
zH8l8sQf/TCatRkmucQ96jV8XgzKeV5G/t6EMP8p6pWr5a+LJGgPH/l47fv1663aStcY
yQdQ==
MIME-Version: 1.0
Received: by 10.224.202.136 with SMTP id fe8mr43184140qab.17.1343925806061;
Thu, 02 Aug 2012 09:43:26 -0700 (PDT)
Received: by 10.49.120.7 with HTTP; Thu, 2 Aug 2012 09:43:25 -0700 (PDT)
X-Originating-IP: [2001:4830:1603:2:21c:c0ff:fe79:c8c2]
Date: Thu, 2 Aug 2012 12:43:25 -0400
Message-ID: <CA+8xBpfeoNOte=GFGqAT7+4U+JCa4DP8CkEupe+oKdJL1dMFFQ@mail.gmail.com>
From: Jeff Garzik <jgarzik@exmulti.com>
To: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQmXlGuMFZ+r9yeeiLq+Sh3S+gy8635zyS60rNW212352ET+Zzf0WlW+1nhsYp7FiEiT5rjj
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
X-Headers-End: 1SwyUl-00083B-IX
Subject: [Bitcoin-development] Version 0.7 release planning
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Thu, 02 Aug 2012 16:43:32 -0000
There seems to be consensus that we should go ahead and do a release,
before leveldb or ultraprune or anything major lands. There is no
major landmark feature, but just a useful collection of small changes.
It seems like a good time to Release Early, Release Often and make a
checkpoint release.
Some rough draft release notes were dumped in
https://github.com/bitcoin/bitcoin/blob/master/doc/release-notes.txt
Opening the floor... What do we collectively want to happen, before
0.7 release? What is the todo list for 0.7?
After cleaning out some pull requests yesterday, and looking at the
list today, I see
1) CreateNewBlock: Child-pays-for-parent / Add transaction fee later
luke-jr https://github.com/bitcoin/bitcoin/pull/1647
2) Translations update 2012-08-01 (fetched from Transifex)
Diapolo https://github.com/bitcoin/bitcoin/pull/1644
3) Add address groupings RPC from coderrr's coincontrol patches.
gmaxwell https://github.com/bitcoin/bitcoin/pull/1642
4) Add 'mempool' P2P command, and extend 'getdata' behavior
jgarzik https://github.com/bitcoin/bitcoin/pull/1641
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
6) JSON-RPC method: prioritisetransaction <txid> <priority delta>
luke-jr https://github.com/bitcoin/bitcoin/pull/1583
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
9) WE MUST PICK ONE: RPC: lock push-down, preparing for
parallelization opportunities
jgarzik https://github.com/bitcoin/bitcoin/pull/1494
or
RPC: add facility to enable RPCs to run outside cs_main, wallet locks
jgarzik https://github.com/bitcoin/bitcoin/pull/1493
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
Devs -- feel free to commit directly to doc/release-notes.txt if there
is a missing commit, or something that may be better described.
--
Jeff Garzik
exMULTI, Inc.
jgarzik@exmulti.com
|
