From: Matt Corallo <lf-lists@mattcorallo.com>
To: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: [bitcoin-dev] Bitcoin Core 0.13.1 release candidate 3
Date: Tue, 25 Oct 2016 17:47:37 +0000 [thread overview]
Message-ID: <580F9AB9.8010907@mattcorallo.com> (raw)
Due to a relatively trivial fix for an out-of-place assertion in rc2
(see
https://github.com/bitcoin/bitcoin/commit/58d4fa7da30cb57e5fc3dca62f49a64e126c76cd),
0.13.1rc3 was tagged and is now available on github either via git or at
https://github.com/bitcoin/bitcoin/releases/tag/v0.13.1rc3.
Because of the simplicity of the change, it was decided that 0.13.1
should not be delayed as a result, and thus no official binaries will be
made available for rc3.
However, any additional testing which folks have time for before final
tag on Thursday would be significantly welcomed.
As usual please report bugs using the issue tracker on github at
https://github.com/bitcoin/bitcoin/issues
Thanks,
Matt
reply other threads:[~2016-10-25 17:47 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=580F9AB9.8010907@mattcorallo.com \
--to=lf-lists@mattcorallo.com \
--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