From: "Wladimir J. van der Laan" <laanwj@gmail.com>
To: Bitcoin development mailing list
<bitcoin-development@lists.sourceforge.net>
Subject: [Bitcoin-development] Bitcoin core 0.11.0 release candidate 2 available
Date: Thu, 18 Jun 2015 10:56:37 +0200 [thread overview]
Message-ID: <20150618085636.GC21275@amethyst.visucore.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hello,
I've just uploaded Bitcoin Core 0.11.0rc2 executables to:
https://bitcoin.org/bin/bitcoin-core-0.11.0/test/
The source code can be found in the source tarball or in git under the tag 'v0.11.0rc2'
Preliminary release notes can be found here:
https://github.com/bitcoin/bitcoin/blob/0.11/doc/release-notes.md
Changes since rc1:
- - #6274 `4d9c7fe` Add option `-alerts` to opt out of alert system
- - #5985 `37b4e42` Fix removing of orphan transactions
- - #6221 `6cb70ca` Prune: Support noncontiguous block files
- - #6256 `fce474c` Use best header chain timestamps to detect partitioning
- - #6244 `0401aa2` configure: Detect (and reject) LibreSSL
- - #6269 `95aca44` gitian: Use the new bitcoin-detached-sigs git repo for OSX signatures
- - #6285 `ef1d506` Fix scheduler build with some boost versions.
- - #6280 `25c2216` depends: fix Boost 1.55 build on GCC 5
- - #6276 `c9fd907` Fix getbalance * 0
- - #6264 `94cd705` Remove translation for -help-debug options
- - #6286 `3902c15` Remove berkeley-db4 workaround in MacOSX build docs
Thanks to everyone that participated in development, translation or in the gitian build process,
Wladimir
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBCgAGBQJVgoeFAAoJEHSBCwEjRsmmkggH/3jyzuPXDpUpCpfzyDZDW4CO
GRqIZwCa8vY9Gv9T0mX5jLXOfXpPAMyzWnCz2Eqh0hRLHK8WzObPqdX+3KLaaoO/
rOroDCG7AUZB4GaodSZURqJm8RmnNtWNckK7GBwXbZ7qNZrkpRNUh1z2JsatZdum
bUTBHX6Z9jW4HCmMZNn5lv5hRwu3XzFSi1uu9VyleVnIvdSbyjMhfjKn1VG0Rcnw
kTrCUgJccMP0htNGpIPni14PTak16ULs7KXMPNtpgB/lo/4LhDLGTivXL5ntjQXX
gQarGdh9eCqazHyIMSHTj4eO3GvLNUCHp3wM6YTiEhABkkWL3wRwn8yqMRf0EWE=
=GCM7
-----END PGP SIGNATURE-----
reply other threads:[~2015-06-18 8:56 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=20150618085636.GC21275@amethyst.visucore.com \
--to=laanwj@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