From: "Wladimir J. van der Laan" <laanwj@gmail•com>
To: Bitcoin development mailing list <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] Bitcoin Core 0.12.0 release candidate 2 available
Date: Mon, 25 Jan 2016 13:09:38 +0100 [thread overview]
Message-ID: <20160125120938.GC17769@amethyst.visucore.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Binaries for bitcoin Core version 0.12.0rc2 are available from:
https://bitcoin.org/bin/bitcoin-core-0.12.0/test/
Source code can be found on github under the signed tag
https://github.com/bitcoin/bitcoin/tree/v0.12.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 here:
https://github.com/bitcoin/bitcoin/blob/0.12/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.12.0.
Diff since rc1:
- - #7222 `e25b158` RPC: indicate which transactions are replaceable
- - #7386 `da83ecd` Add option `-permitrbf` to set transaction replacement policy
- - #7290 `b16b5bc` Add missing options help
- - #7387 `f4b2ce8` Get rid of inaccurate ScriptSigArgsExpected
- - #7381 `621bbd8` [walletdb] Fix syntax error in key parser
- - #7327 `b16b5bc` [Wallet] Transaction View: LastMonth calculation fixed
- - #7364 `7726c48` [qt] Windows: Make rpcconsole monospace font larger
Please report bugs using the issue tracker at github:
https://github.com/bitcoin/bitcoin/issues
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBCgAGBQJWphBHAAoJEHSBCwEjRsmmh0EIALopACCwaCYRt9vl6fadDLxL
JMTyEPsGUaEX82iwuXeAhdReyvZDlC00ACZy6agp7oOuS1ryqOeYAsc33N+WtHE0
iETNyvRZVD1ASopHkdJrRW1a9X63Yvcvk/d6nVbO5auUAG5gPUFLrSTrqpSzR2D4
QtY1ofifXrYdqdQmPFJ5hnWg/Z1rko99sD8Pu3ebD6Dof5zuvJKHkLmXunGGXn/n
GOn8roS5LXEFHwCcL0zgNzfDywt/dhKiUHMKSNPsnz5qEDRg7WPzsNiQA/HVDlcp
v6akQ4ykZ56Lik8cVLi0NRW2dozSDti/XKBfWQHqWjGUJGUOS+lPJaWLv81oMwc=
=WlQm
-----END PGP SIGNATURE-----
reply other threads:[~2016-01-25 12:09 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=20160125120938.GC17769@amethyst.visucore.com \
--to=laanwj@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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