public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "Wladimir J. van der Laan" <laanwj@gmail•com>
To: bitcoin-dev@lists•linuxfoundation.org,
	bitcoin-core-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Bitcoin Core 0.12.1 release candidate 1 available
Date: Mon, 11 Apr 2016 11:12:13 +0200	[thread overview]
Message-ID: <20160411091213.GA10644@amethyst.visucore.com> (raw)
In-Reply-To: <20160411073706.GA10244@amethyst.visucore.com>

That's rc2, not rc1 (thanks btcdrak for noticing).
rc1 was DOA - see meeting minutes from Thursday.
Link for the tag:

https://github.com/bitcoin/bitcoin/tree/v0.12.1rc2

The other links and downloads are correct.

Wladimir

On Mon, Apr 11, 2016 at 09:37:06AM +0200, Wladimir J. van der Laan wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
> 
> Binaries for bitcoin Core version 0.12.1rc1 are available from:
> 
>     https://bitcoin.org/bin/bitcoin-core-0.12.1/test.rc2/
> 
> Source code can be found on github under the signed tag
> 
>     https://github.com/bitcoin/bitcoin/tree/v0.12.1rc1
> 
> This is a release candidate for a new minor version release, including the
> BIP9, BIP68 and BIP112 softfork, various bugfixes and updated translations.
> 
> 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.1.
> 
> Please report bugs using the issue tracker at github:
> 
>     https://github.com/bitcoin/bitcoin/issues
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
> 
> iQEcBAEBCgAGBQJXC1QSAAoJEHSBCwEjRsmmtk4H/1C74eLLVwzOhrrWNx34ANcz
> uiyIlkXnMmX+iHWaSC8XdcBOEc4/+YOgDK0KU+FRG6bNDengPKqf8mPDEvyXU/H+
> /ed2W9Q0DQ/jxyeKOOVlMWhKCZWQRisxhadB0LAiny2QLsBojTrJtziGIOYXp4Qt
> xI3GstbUr42da8kL8NoKxQt6na5FrGiuRAQeucwcoHi1QQodd7R7vA2b84N1ECrr
> KWbCfw6a9qHDmk2Vy+9CqGtESHuVW04B+79ui+Dgsh6frG9UH5G7WP4ziUcwm625
> CEEbi/cIrpzEOSo4S5ukFhYK6I3o67uxvV8Nc3ocI1UmC4d2BUvAMalBGMgjENg=
> =oPfq
> -----END PGP SIGNATURE-----


      reply	other threads:[~2016-04-11  9:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-11  7:37 Wladimir J. van der Laan
2016-04-11  9:12 ` Wladimir J. van der Laan [this message]

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=20160411091213.GA10644@amethyst.visucore.com \
    --to=laanwj@gmail$(echo .)com \
    --cc=bitcoin-core-dev@lists$(echo .)linuxfoundation.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