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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <laanwj@gmail.com>) id 1TJU1G-00065O-Vs
for bitcoin-development@lists.sourceforge.net;
Wed, 03 Oct 2012 18:50:07 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.212.181 as permitted sender)
client-ip=209.85.212.181; envelope-from=laanwj@gmail.com;
helo=mail-wi0-f181.google.com;
Received: from mail-wi0-f181.google.com ([209.85.212.181])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1TJU1G-0004um-4U
for bitcoin-development@lists.sourceforge.net;
Wed, 03 Oct 2012 18:50:06 +0000
Received: by wibhq12 with SMTP id hq12so2108456wib.10
for <bitcoin-development@lists.sourceforge.net>;
Wed, 03 Oct 2012 11:50:00 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.180.91.71 with SMTP id cc7mr6877790wib.2.1349290199815; Wed,
03 Oct 2012 11:49:59 -0700 (PDT)
Received: by 10.194.6.73 with HTTP; Wed, 3 Oct 2012 11:49:59 -0700 (PDT)
In-Reply-To: <CABsx9T1v9Rfm_d7DcfbkkHEC96CwTNNp4_E1G97UBXqVHjVyOw@mail.gmail.com>
References: <CABsx9T1v9Rfm_d7DcfbkkHEC96CwTNNp4_E1G97UBXqVHjVyOw@mail.gmail.com>
Date: Wed, 3 Oct 2012 20:49:59 +0200
Message-ID: <CA+s+GJAOmQDo=zTF-b4r5X6CjogJtd2gQ0VeGoHZboTB6o+wFQ@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Gavin Andresen <gavinandresen@gmail.com>
Content-Type: text/plain; charset=UTF-8
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
(laanwj[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: 1TJU1G-0004um-4U
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [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 18:50:07 -0000
On Wed, Oct 3, 2012 at 7:49 PM, Gavin Andresen <gavinandresen@gmail.com> wrote:
> 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.
>
> "Handle corrupt wallets gracefully" :
> https://github.com/bitcoin/bitcoin/pull/1895
We definitely need that one in.
>
> This pull request:
>
> "Add -reindex, to perform in-place reindexing of blockchain data
> files" : https://github.com/bitcoin/bitcoin/pull/1870
Agreed
>
> Are there any other very-high-priority pull requests that should go
> into a 0.7.1 release?
I think we should also pull #1859 "add LOCK() for proxy related
data-structures" Missing synchronization primitives are a sure way to
get reports about random crashes.
The rest can wait.
Wladimir
|
