From: Gavin Andresen <gavinandresen@gmail.com>
To: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: [Bitcoin-development] 0.7.1 release candidate 1 ready for testing
Date: Thu, 11 Oct 2012 11:46:10 -0400 [thread overview]
Message-ID: <CABsx9T2Y+Ku1DcvWGS+c3p+qRFKbM8O=-CuL=1kC0TZdK1Sz5A@mail.gmail.com> (raw)
Any progress on a release candidate QA sanity testing plan?
Bitcoin version 0.7.1 release candidate 1 is now available from:
http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.7.1/test/
This is a bug-fix minor release.
New features
------------
* Added a boolean argument to the RPC 'stop' command, if true sets
-detachdb to create standalone database .dat files before shutting down.
* -salvagewallet command-line option, which moves any existing wallet.dat
to wallet.{timestamp}.dat and then attempts to salvage public/private
keys and master encryption keys (if the wallet is encrypted) into
a new wallet.dat. This should only be used if your wallet becomes
corrupted, and is not intended to replace regular wallet backups.
* Import $DataDir/bootstrap.dat automatically, if it exists.
Dependency changes
------------------
* Qt 4.8.2 for Windows builds
* openssl 1.0.1c
Bug fixes
---------
* When running -testnet, use RPC port 18332 by default.
* Better detection and handling of corrupt wallet.dat and blkindex.dat files.
Previous versions would crash with a DB_RUNRECOVERY exception, this
version detects most problems and tells you how to recover if it
cannot recover itself.
* Fixed an uninitialized variable bug that could cause transactions to
be reported out of order.
* Fixed a bug that could cause occasional crashes on exit.
* Warn the user that they need to create fresh wallet backups after they
encrypt their wallet.
--
--
Gavin Andresen
next reply other threads:[~2012-10-11 15:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 15:46 Gavin Andresen [this message]
2012-10-11 15:59 ` [Bitcoin-development] 0.7.1 release candidate 1 ready for testing Jeff Garzik
2012-10-11 16:17 ` Arklan Uth Oslin
2012-10-11 17:45 ` steve
2012-10-11 17:51 ` Arklan Uth Oslin
2012-10-11 19:20 ` Jeff Garzik
2012-10-11 20:08 ` Arklan Uth Oslin
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='CABsx9T2Y+Ku1DcvWGS+c3p+qRFKbM8O=-CuL=1kC0TZdK1Sz5A@mail.gmail.com' \
--to=gavinandresen@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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