From: Luke Dashjr <luke@dashjr•org>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: [bitcoin-dev] Bitcoin Knots 0.14.0 release candidate 2 available
Date: Tue, 28 Feb 2017 20:59:44 +0000 [thread overview]
Message-ID: <201702282059.44714.luke@dashjr.org> (raw)
Release candidate 2 of a new major Bitcoin Knots release, version 0.14.0, has
been made available.
This is a release candidate for a new major version release, including new
features, various bugfixes and performance improvements.
Preliminary release notes for the release can be found here:
https://github.com/bitcoinknots/bitcoin/blob/v0.14.0.knots20170227.rc2/doc/release-notes.md
Binaries can be downloaded from:
http://bitcoinknots.org/files/0.14.x/0.14.0.knots20170227.rc2/
Please take care to verify the PGP signature of all downloads.
Source code can be found on GitHub under the signed tag
https://github.com/bitcoinknots/bitcoin/tree/v0.14.0.knots20170227.rc2
Release candidates are test versions for releases. When no critical problems
are found, this release candidate will be tagged as 0.14.0 final, otherwise
a new rc will be made available after these are solved.
Please report bugs using the issue tracker at GitHub:
https://github.com/bitcoinknots/bitcoin/issues
reply other threads:[~2017-02-28 20:59 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=201702282059.44714.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--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