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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <laanwj@gmail.com>) id 1YspHn-0005YJ-A7
for bitcoin-development@lists.sourceforge.net;
Thu, 14 May 2015 09:18:35 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 74.125.82.47 as permitted sender)
client-ip=74.125.82.47; envelope-from=laanwj@gmail.com;
helo=mail-wg0-f47.google.com;
Received: from mail-wg0-f47.google.com ([74.125.82.47])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1YspHl-0001bH-FG
for bitcoin-development@lists.sourceforge.net;
Thu, 14 May 2015 09:18:35 +0000
Received: by wgin8 with SMTP id n8so68751545wgi.0
for <bitcoin-development@lists.sourceforge.net>;
Thu, 14 May 2015 02:18:27 -0700 (PDT)
X-Received: by 10.180.206.19 with SMTP id lk19mr2770047wic.94.1431595107445;
Thu, 14 May 2015 02:18:27 -0700 (PDT)
Received: from amethyst.visucore.com (dhcp-089-098-016-041.chello.nl.
[89.98.16.41]) by mx.google.com with ESMTPSA id
bg4sm34153485wjc.10.2015.05.14.02.18.26
for <bitcoin-development@lists.sourceforge.net>
(version=TLSv1.2 cipher=RC4-SHA bits=128/128);
Thu, 14 May 2015 02:18:26 -0700 (PDT)
Date: Thu, 14 May 2015 11:18:26 +0200
From: "Wladimir J. van der Laan" <laanwj@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Message-ID: <20150514091825.GA15439@amethyst.visucore.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)
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: 1YspHl-0001bH-FG
Subject: [Bitcoin-development] Bitcoin Core 0.10.1 release candidate 2
available
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, 14 May 2015 09:18:35 -0000
Binaries for bitcoin Core version 0.10.2rc1 are now available from:
https://bitcoin.org/bin/0.10.2/test
Source code can be found on github under the signed tag
https://github.com/bitcoin/bitcoin/tree/v0.10.2rc1
This is a release candidate for a minor version release, with mainly a fix for
a bug that affected Windows users with non-ASCII characters in the data directory.
The release also contains translation updates.
If you experienced no issues with 0.10.1, there is no need to upgrade.
Preliminary release notes for the 0.10.2 release can be found here:
https://github.com/bitcoin/bitcoin/blob/v0.10.2rc1/doc/release-notes.md
Release candidates are test runs for releases, when no critical
problems are found this release candidate will be tagged as 0.10.2.
Please report bugs using the issue tracker at github:
https://github.com/bitcoin/bitcoin/issues
|
