-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Binaries for bitcoin Core version 0.16.0rc4 are available from:

    https://bitcoincore.org/bin/bitcoin-core-0.16.0/test.rc4/

Source code can be found on github under the signed tag

    https://github.com/bitcoin/bitcoin/tree/v0.16.0rc4

This is a release candidate for a new major version release.

Preliminary release notes for the release can be found here:

    https://github.com/bitcoin-core/bitcoin-devwiki/wiki/0.16.0-Release-notes

Release candidates are test versions for releases. When no critical problems
are found, this release candidate will be tagged as 0.16.0.

Changes since rc4:

- - #12415 `f893824` Interrupt loading thread after shutdown request (promag)
- - #12392 `0f61651` Fix ignoring tx data requests when fPauseSend is set on a 
peer (TheBlueMatt)
- - #12427 `3762ac1` Make signrawtransaction accept P2SH-P2WSH redeemscripts 
(sipa)
- - #12349 `ad10b90` shutdown: fix crash on shutdown with reindex-chainstate 
(theuni)
- - #12424 `ff44101` Fix rescan test failure due to unset g_address_type, 
g_change_type (ryanofsky)
- - #12388 `e2431d1` travis: Full clone for git subtree check (MarcoFalke)
- - #12422 `4d54e7a` util: Make LockDirectory thread-safe, consistent, and fix 
OpenBSD 6.2 build (laanwj)

Please report bugs using the issue tracker at github:

    https://github.com/bitcoin/bitcoin/issues

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCgAGBQJain4iAAoJEB5K7WKYbNJduNQIAJbZKs9OCbML5QjNpgjBhGXD
oWv23RZti3OLJvOa5I0pM2UuofKHrZmGj1zZLhtySvm+pHs0c2iL8fur8eLICawZ
VhCIGmtDwtp7OFXMPIv3t7I3bqnv2fo48pnQvFjFZS5+yDqIVkZV/LjWTPqDOhoF
akTtBw3Hyi14sUItYTSDokF+rZmvrI/cOE2I/EdvHUm+zjLrI6jHWtgIgRAey8M7
S2VwaxbTM88sx9cvd1dU0fUpR8ayd2bAHWzcOPNls3K3nnid/qeaBY/bHMWeB0Bp
UqKCH4kuUs2Qgh3XMyLt8uxu/xM5fqLdXElkqf68YGWrJkEpzJo/pBI6MZwP5+E=
=TZiH
-----END PGP SIGNATURE-----
_______________________________________________
bitcoin-core-dev mailing list
bitcoin-core-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-core-dev

Reply via email to