summaryrefslogtreecommitdiff
path: root/e8/fc1859dc18d80b3f38605fde41058b77676006
blob: fd77c160b0fb3ded875a19e07ff690814a802bd3 (plain)
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
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <laanwj@gmail.com>) id 1YuiWL-0007E3-Rl
	for bitcoin-development@lists.sourceforge.net;
	Tue, 19 May 2015 14:29:25 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.213.51 as permitted sender)
	client-ip=209.85.213.51; envelope-from=laanwj@gmail.com;
	helo=mail-yh0-f51.google.com; 
Received: from mail-yh0-f51.google.com ([209.85.213.51])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1YuiWI-0000UJ-AF
	for bitcoin-development@lists.sourceforge.net;
	Tue, 19 May 2015 14:29:25 +0000
Received: by yhcb70 with SMTP id b70so4616916yhc.0
	for <bitcoin-development@lists.sourceforge.net>;
	Tue, 19 May 2015 07:29:16 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.236.108.129 with SMTP id q1mr27642981yhg.28.1432045756758;
	Tue, 19 May 2015 07:29:16 -0700 (PDT)
Received: by 10.13.250.69 with HTTP; Tue, 19 May 2015 07:29:16 -0700 (PDT)
In-Reply-To: <20150519134408.GB22164@amethyst.visucore.com>
References: <20150519134408.GB22164@amethyst.visucore.com>
Date: Tue, 19 May 2015 14:29:16 +0000
Message-ID: <CA+s+GJB=MqFs1aVCeyXj0b3fjpBe+6S6Y=WUcKcMzQv2KGAzQQ@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
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: 1YuiWI-0000UJ-AF
Subject: Re: [Bitcoin-development] Bitcoin Core 0.10.2 released
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: Tue, 19 May 2015 14:29:25 -0000

Bitcoin Core version 0.10.2 is now available from:

  <https://bitcoin.org/bin/bitcoin-core-0.10.2/>

The distribution is also available as torrent:

   https://bitcoin.org/bin/bitcoin-core-0.10.2/bitcoin-0.10.2.torrent

   magnet:?xt=3Durn:btih:746a616aa8de97856c207e7a899c7ee315e8c44d&dn=3Dbitc=
oin-core-0.10.2&tr=3Dudp%3A%2F%2Ftracker.openbittorrent.com%3A80%2Fannounce=
&tr=3Dudp%3A%2F%2Ftracker.publicbt.com%3A80%2Fannounce&tr=3Dudp%3A%2F%2Ftra=
cker.ccc.de%3A80%2Fannounce&tr=3Dudp%3A%2F%2Ftracker.coppersurfer.tk%3A6969=
&tr=3Dudp%3A%2F%2Fopen.demonii.com%3A1337&ws=3Dhttps%3A%2F%2Fbitcoin.org%2F=
bin%2

The source code can be found in git under the tag `v0.10.2`, or in
`bitcoin-0.10.2.tar.gz` in the distribution.

This is a new minor version release, bringing minor bug fixes and translati=
on
updates. It is only necessary to upgrade to this version when unable
to start the
application on Windows with 0.10.1.

Please report bugs using the issue tracker at github:

  <https://github.com/bitcoin/bitcoin/issues>

Upgrading and downgrading
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

How to Upgrade
--------------

If you are running an older version, shut it down. Wait until it has comple=
tely
shut down (which might take a few minutes for older versions), then run the
installer (on Windows) or just copy over /Applications/Bitcoin-Qt (on Mac) =
or
bitcoind/bitcoin-qt (on Linux).

Downgrade warning
------------------

Because release 0.10.0 and later makes use of headers-first synchronization=
 and
parallel block download (see further), the block files and databases are no=
t
backwards-compatible with pre-0.10 versions of Bitcoin Core or other softwa=
re:

* Blocks will be stored on disk out of order (in the order they are
received, really), which makes it incompatible with some tools or
other programs. Reindexing using earlier versions will also not work
anymore as a result of this.

* The block index database will now hold headers for which no block is
stored on disk, which earlier versions won't support.

If you want to be able to downgrade smoothly, make a backup of your entire =
data
directory. Without this your node will need start syncing (or importing fro=
m
bootstrap.dat) anew afterwards. It is possible that the data from a complet=
ely
synchronised 0.10 node may be usable in older versions as-is, but this is n=
ot
supported and may break as soon as the older version attempts to reindex.

This does not affect wallet forward or backward compatibility.

Notable changes
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

This fixes a serious problem on Windows with data directories that
have non-ASCII
characters (https://github.com/bitcoin/bitcoin/issues/6078).

For other platforms there are no notable changes.

For the notable changes in 0.10, refer to the release notes
at https://github.com/bitcoin/bitcoin/blob/v0.10.0/doc/release-notes.md

0.10.2 Change log
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Detailed release notes follow. This overview includes changes that
affect external
behavior, not code moves, refactors or string updates.

Wallet:
- `824c011` fix boost::get usage with boost 1.58

Miscellaneous:
- `da65606` Avoid crash on start in TestBlockValidity with gen=3D1.
- `424ae66` don't imbue boost::filesystem::path with locale "C" on
windows (fixes #6078)

Credits
=3D=3D=3D=3D=3D=3D=3D

Thanks to everyone who directly contributed to this release:

- Cory Fields
- Gregory Maxwell
- Jonas Schnelli
- Wladimir J. van der Laan

And all those who contributed additional code review and/or security resear=
ch:

- dexX7
- Pieter Wuille
- vayvanne

As well as everyone that helped translating on
[Transifex](https://www.transifex.com/projects/p/bitcoin/).

On Tue, May 19, 2015 at 1:44 PM, Wladimir J. van der Laan
<laanwj@gmail.com> wrote:
>