From: Gavin Andresen <gavinandresen@gmail•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] Version 0.6 release candidate 5 binaries
Date: Mon, 26 Mar 2012 19:40:18 -0400 [thread overview]
Message-ID: <4F70FE62.8040807@gmail.com> (raw)
-----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-----
reply other threads:[~2012-03-26 23:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F70FE62.8040807@gmail.com \
--to=gavinandresen@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox