From: Luke Dashjr <luke@dashjr•org>
To: Bitcoin development mailing list
<bitcoin-dev@lists•linuxfoundation.org>,
"bitcoin-discuss@lists•linuxfoundation.org"
<bitcoin-discuss@lists•linuxfoundation.org>
Subject: [bitcoin-dev] Bitcoin Knots 0.12.0.knots20160226 release candidate 1 available
Date: Tue, 1 Mar 2016 17:12:34 +0000 [thread overview]
Message-ID: <201603011712.35416.luke@dashjr.org> (raw)
Binaries for Bitcoin Knots version 0.12.0.knots20160226.rc1 are available from:
https://bitcoinknots.org/files/0.12.x/0.12.0.knots20160226/test/rc1/
Source code can be found on GitHub under the signed tag:
https://github.com/bitcoinknots/bitcoin/tree/v0.12.0.knots20160226.rc1
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/bitcoinknots/bitcoin/blob/0.12.x-knots/doc/release-notes.md
Release candidates are test versions for releases. When no critical problems
are found, this release candidate will be tagged as final.
Please report bugs using the issue tracker at GitHub:
https://github.com/bitcoinknots/bitcoin/issues
Additional Gitian signatures are welcome. Please submit via GitHub pull
request to:
https://github.com/bitcoinknots/gitian.sigs
reply other threads:[~2016-03-01 17:13 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=201603011712.35416.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=bitcoin-discuss@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