summaryrefslogtreecommitdiff
path: root/f5/fcc8420b993d1c21e5a4e66294a97716ef07d5
blob: d144d03e08807660d2c9ed57eb25bb658beb040c (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
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
	helo=mx.sourceforge.net)
	by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <gavinandresen@gmail.com>) id 1SCJWX-0008IH-Ug
	for bitcoin-development@lists.sourceforge.net;
	Mon, 26 Mar 2012 23:40:30 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.216.175 as permitted sender)
	client-ip=209.85.216.175; envelope-from=gavinandresen@gmail.com;
	helo=mail-qc0-f175.google.com; 
Received: from mail-qc0-f175.google.com ([209.85.216.175])
	by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1SCJWV-0000mz-Mu
	for bitcoin-development@lists.sourceforge.net;
	Mon, 26 Mar 2012 23:40:29 +0000
Received: by qcso7 with SMTP id o7so4151180qcs.34
	for <bitcoin-development@lists.sourceforge.net>;
	Mon, 26 Mar 2012 16:40:22 -0700 (PDT)
Received: by 10.229.78.165 with SMTP id l37mr9034508qck.142.1332805222104;
	Mon, 26 Mar 2012 16:40:22 -0700 (PDT)
Received: from Sparky-2.local (pool-96-240-193-190.spfdma.east.verizon.net.
	[96.240.193.190])
	by mx.google.com with ESMTPS id fo9sm23461400qab.21.2012.03.26.16.40.20
	(version=SSLv3 cipher=OTHER); Mon, 26 Mar 2012 16:40:21 -0700 (PDT)
Message-ID: <4F70FE62.8040807@gmail.com>
Date: Mon, 26 Mar 2012 19:40:18 -0400
From: Gavin Andresen <gavinandresen@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6;
	rv:11.0) Gecko/20120313 Thunderbird/11.0
MIME-Version: 1.0
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
X-Enigmail-Version: 1.4
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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
	(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
X-Headers-End: 1SCJWV-0000mz-Mu
Subject: [Bitcoin-development] Version 0.6 release candidate 5 binaries
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: Mon, 26 Mar 2012 23:40:30 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Barring any last-minute showstopper issues, the plan is for release
candidate 5 to become the official 0.6.0 release on Wednesday.

So please help look for last-minute showstopper issues:

https://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.6.0/test/

The major changes from release candidate 4:

+ Much faster writing of blkindex.dat during initial blockchain
download (by modifying the default bdb environment cache settings)

+ A new policy for wallet.dat upgrades: use the old format unless the
user either uses a feature that requires an upgrade (encrypts the
wallet) or explicitly requests that the wallet be upgraded using the
new -upgradewallet option. New wallets will use new features (for 0.6,
the only new wallet feature is compressed public keys).

+ bugfix introduced in rc4 for an assertion failure that could occur
during blockchain reorganizations

+ New code for managing the addr.dat file that prevents an attacker
from filling it with bogus entries.


- -- 
- --
Gavin Andresen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk9w/mIACgkQdYgkL74406gafACdHYn6QI6QoKhkf22e0My2jCWa
IPkAn3YnNeMEmG8N6xEyCdNx3MTjgkcF
=CRL2
-----END PGP SIGNATURE-----