From: Wladimir <laanwj@gmail•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] [ANN] 0.10.0rc2 has been tagged
Date: Mon, 12 Jan 2015 11:31:33 +0000 [thread overview]
Message-ID: <CA+s+GJDx9CFobm+4nNt_zKmDZMHnKUoVDmHu2wByihD8qTBTRA@mail.gmail.com> (raw)
I've just tagged 0.10.0rc2 in git.
To fetch, build, and test (see also doc/build-*.md):
```
git clone -b v0.10.0rc2 https://github.com/bitcoin/bitcoin.git bitcoin-0.10
cd bitcoin-0.10
./autogen.sh
./configure
make
make check
```
Note: This includes the changes required for interoperability with
OpenSSL 1.0.1k.
Notable changes relative to v0.10.0rc1:
- 4e7c219 Catch UTXO set read errors and shutdown
- a3a7317 Introduce 10 minute block download timeout
- 12b7c44 Improve robustness of DER recoding code
- 76ce5c8 fail immediately on an empty signature
- 2d375fe depends: bump openssl to 1.0.1k
- ace39db consensus: guard against openssl's new strict DER checks
- 263b65e tests: run sanity checks in tests too
- e2677d7 Fix smartfees test for change to relay policy
- b7a4ecc Build: Only check for boost when building code that requires it
- 867c600 Catch LevelDB errors during flush
- 008138c Bugfix: only track UTXO modification after lookup
- 3022e7d Require sufficent priority for relay of free transactions
- 06fdf32 bitcoin-tx: Fix JSON validation of prevtxs
- 58fda4d Update seed IPs, based on bitcoin.sipa.be crawler data
- 94b362d On close of splashscreen interrupt verifyDB
- 1eadfd9 Bugfix: prioritisetransaction: Do some basic sanity checking on txid
- 18021d0 Remove bitnodes.io from dnsseeds.
- b790d13 English translation update
- 8543b0d Correct tooltip on address book page
- 87d43a3 rpcserver: attempt to fix uncaught exception.
- 06ca065 Fix CScriptID(const CScript& in) in empty script case
Wladmir
reply other threads:[~2015-01-12 11:31 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=CA+s+GJDx9CFobm+4nNt_zKmDZMHnKUoVDmHu2wByihD8qTBTRA@mail.gmail.com \
--to=laanwj@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