From: Drak <drak@zikula.org>
To: Wladimir <laanwj@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] 0.8.6 release candidate 1
Date: Mon, 9 Dec 2013 15:42:43 +0000 [thread overview]
Message-ID: <CANAnSg1bmox9rAETgVVsyD8kVyvpiZ9vxddSEaR0i5a8c9riBw@mail.gmail.com> (raw)
In-Reply-To: <CA+s+GJDMSvpY_0p05RfEh=P_uuLPGFezBiNY+e7aktbUt8-oyQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 754 bytes --]
On 9 December 2013 15:35, Wladimir <laanwj@gmail.com> wrote:
>
> On Mon, Dec 9, 2013 at 4:19 PM, Drak <drak@zikula.org> wrote:
>
>>
>> IMO, to avoid that, no files should be placed online unless they are the
>> official release.
>>
>
> They *are* the official release as soon as they're uploaded. We may wait
> for some extra gitian builds to be more confident and make the announcement
> on the forums and such, but the downloads themselves don't change anymore.
>
That is exactly the point and the moment they are publicly available you
cannot stop people talking about it or noticing it, or posting official
looking sticky posts at bitcointalk like this one:
https://bitcointalk.org/index.php?topic=364353.0. Was that an official
announcement?
Drak
[-- Attachment #2: Type: text/html, Size: 1725 bytes --]
next prev parent reply other threads:[~2013-12-09 15:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-06 6:52 [Bitcoin-development] 0.8.6 release candidate 1 Gavin Andresen
2013-12-08 23:07 ` Warren Togami Jr.
2013-12-09 6:14 ` Gavin Andresen
2013-12-09 7:34 ` Warren Togami Jr.
2013-12-09 13:39 ` Drak
2013-12-09 13:52 ` Roy Badami
2013-12-09 14:55 ` Drak
2013-12-09 15:07 ` Gregory Maxwell
2013-12-09 15:19 ` Drak
2013-12-09 15:25 ` Gregory Maxwell
2013-12-09 15:35 ` Wladimir
2013-12-09 15:42 ` Drak [this message]
2013-12-09 15:44 ` Wladimir
2013-12-09 19:06 ` Jeff Garzik
2013-12-10 7:23 ` Roy Badami
2013-12-10 7:47 ` Wladimir
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=CANAnSg1bmox9rAETgVVsyD8kVyvpiZ9vxddSEaR0i5a8c9riBw@mail.gmail.com \
--to=drak@zikula.org \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=laanwj@gmail.com \
/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