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
|
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 <gavinandresen@gmail.com>) id 1TJT4c-00055f-2V
for bitcoin-development@lists.sourceforge.net;
Wed, 03 Oct 2012 17:49:30 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 74.125.82.175 as permitted sender)
client-ip=74.125.82.175; envelope-from=gavinandresen@gmail.com;
helo=mail-we0-f175.google.com;
Received: from mail-we0-f175.google.com ([74.125.82.175])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1TJT4b-00055s-1g
for bitcoin-development@lists.sourceforge.net;
Wed, 03 Oct 2012 17:49:29 +0000
Received: by weyt44 with SMTP id t44so4700947wey.34
for <bitcoin-development@lists.sourceforge.net>;
Wed, 03 Oct 2012 10:49:22 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.216.29.10 with SMTP id h10mr1633318wea.126.1349286562642; Wed,
03 Oct 2012 10:49:22 -0700 (PDT)
Received: by 10.194.17.138 with HTTP; Wed, 3 Oct 2012 10:49:22 -0700 (PDT)
Date: Wed, 3 Oct 2012 13:49:22 -0400
Message-ID: <CABsx9T1v9Rfm_d7DcfbkkHEC96CwTNNp4_E1G97UBXqVHjVyOw@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: text/plain; charset=ISO-8859-1
X-Spam-Score: -1.1 (-)
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
(gavinandresen[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
0.5 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1TJT4b-00055s-1g
Subject: [Bitcoin-development] 0.7.1 release
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: Wed, 03 Oct 2012 17:49:30 -0000
There is consensus that we need to do a 0.7.1 release to fix the
"click on a bitcoin: URI and nothing happens" bug on Windows.
I would really like to fix the "I upgraded from a binary running an
incompatible version of BDB and now I get a DB_RUNRECOVERY error on
startup" problem, too, and I've got a pull request that fixes half of
that problem (plus a bunch of other "my wallet is broken" cases):
"Handle corrupt wallets gracefully" :
https://github.com/bitcoin/bitcoin/pull/1895
This pull request:
"Add -reindex, to perform in-place reindexing of blockchain data
files" : https://github.com/bitcoin/bitcoin/pull/1870
... could be the basis for fixing the other half of the problem (if
blkindex.dat is bad, delete it and re-create it from the blk000?.dat
files).
Are there any other very-high-priority pull requests that should go
into a 0.7.1 release?
I'd like to pull:
"P2P: Do not request blocks from peers with fewer blocks than us" :
https://github.com/bitcoin/bitcoin/pull/1834
"In listaddressgroupings push down the IsMine check to run on each
input." : https://github.com/bitcoin/bitcoin/pull/1872
... and these which could be considered fixes to the new raw transactions API:
"Add redeemScript to raw transactions API" :
https://github.com/bitcoin/bitcoin/pull/1818
"Add new RPC "lockunspent", to prevent spending of selected outputs" :
https://github.com/bitcoin/bitcoin/pull/1861
--
--
Gavin Andresen
|
