From: Wladimir <laanwj@gmail•com>
To: xor <xor@freenetproject•org>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Bitcoin Core 0.9.4 not on bitcoin.org?
Date: Sun, 1 Feb 2015 21:40:57 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.10.1502012133520.21504@nzrgulfg.ivfhpber.pbz> (raw)
In-Reply-To: <2472472.uuMyyaUxq1@1337h4x0r>
On Sun, 1 Feb 2015, xor wrote:
> Why is that?
v0.9.4 is not really a release, just a tag in git.
It contains merely a workaround for a change in OpenSSL which caused
problems - see Gregory Maxwell's post.
As the releases are statically built against OpenSSL, it is not
necessary to upgrade if you use releases from bitcoin.org. Hence no change
on the site.
(but it can be used by people building from source, or distributions
packages such as the Ubuntu PPA, which unwisely dynamically link OpenSSL)
> Also, is it correct that there wasn't a release candidate before the release?
> Sounds dangerous to me.
Again, there hasn't been any 0.9.4 release, neither a release candidate or
anything else.
Testing and such should be focused on the 0.10 release candidates.
Wladimir
next prev parent reply other threads:[~2015-02-01 20:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-01 20:08 xor
2015-02-01 20:40 ` Wladimir [this message]
2015-02-01 20:41 ` Gregory Maxwell
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=alpine.DEB.2.10.1502012133520.21504@nzrgulfg.ivfhpber.pbz \
--to=laanwj@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=xor@freenetproject$(echo .)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