From: "Wladimir J. van der Laan" <laanwj@gmail.com>
To: bitcoin-dev@lists.linuxfoundation.org,
bitcoin-core-dev@lists.linuxfoundation.org
Subject: [bitcoin-dev] Bitcoin Core 0.13.0 release candidate 2 available
Date: Sun, 31 Jul 2016 15:44:12 +0200 [thread overview]
Message-ID: <20160731134412.GA7172@amethyst.visucore.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Binaries for bitcoin Core version 0.13.0rc2 are available from:
https://bitcoin.org/bin/bitcoin-core-0.13.0/test.rc2/
Source code can be found on github under the signed tag
https://github.com/bitcoin/bitcoin/tree/v0.13.0rc2
This is a release candidate for a new major version release, bringing new
features, bug fixes, as well as other improvements.
Preliminary release notes for the release can be found at
https://github.com/bitcoin/bitcoin/blob/0.13/doc/release-notes.md
Release candidates are test versions for releases. When no critical problems
are found, this release candidate will be tagged as 0.13.0.
Please report bugs using the issue tracker at github:
https://github.com/bitcoin/bitcoin/issues
Notable changes since rc1:
### Build system
- - #8373 `1fe7f40` Fix OSX non-deterministic dmg (theuni)
- - #8358 `cfd1280` Gbuild: Set memory explicitly (default is too low) (MarcoFalke)
### GUI
- - #8407 `45eba4b` Add dbcache migration path (jonasschnelli)
### Wallet
- - #8378 `ebea651` Move SetMinVersion for FEATURE_HD to SetHDMasterKey (pstratem)
- - #8390 `73adfe3` Correct hdmasterkeyid/masterkeyid name confusion (jonasschnelli)
- - #8206 `18b8ee1` Add HD xpriv to dumpwallet (jonasschnelli)
- - #8389 `c3c82c4` Create a new HD seed after encrypting the wallet (jonasschnelli)
### P2P protocol and network code
- - #8408 `b7e2011` Prevent fingerprinting, disk-DoS with compact blocks (sdaftuar)
### Consensus
- - #8412 `8360d5b` libconsensus: Expose a flag for BIP112 (jtimon)
### Mining
- - #8362 `86edc20` Scale legacy sigop count in CreateNewBlock (sdaftuar)
### Block and transaction handling
- - #8381 `f84ee3d` Make witness v0 outputs non-standard (jl2012)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBCgAGBQJXngBiAAoJEHSBCwEjRsmmS5kIAMFiXFua9ruR8Vwu1fNgnWTb
X4tsNOdPScm7jwsFavcwygqZQlDNDURjcocQFcehHgEickBrk6eaplTuB4VJidPG
Aqw+nLrd6M//Ohy+7eke7aCg5/QV7poplM3glwow4gQfoSBvL0ywMEhWEzGL7EPH
FH5pyY9o4QZw5wGdvMWxvYVTLPZkm0W2cSWCHZ0WgzWvTkZ7aMzSQ5F5TXPfjzED
DNuQQRMm9H1H3LJkmWAwjCXLzKNMzjmefLujyEII388s6UoWnA1ufosqb1kMqL+h
kuEelzef4cMBZEvHgfzsvlLmba2DLr7xhwudd3HK2NHSmO/wAUdhbQOQSts9NoY=
=rN68
-----END PGP SIGNATURE-----
reply other threads:[~2016-07-31 13:44 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=20160731134412.GA7172@amethyst.visucore.com \
--to=laanwj@gmail.com \
--cc=bitcoin-core-dev@lists.linuxfoundation.org \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/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