From: Wladimir <laanwj@gmail.com>
To: Drak <drak@zikula.org>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] 0.8.6 release candidate 1
Date: Mon, 9 Dec 2013 16:35:54 +0100 [thread overview]
Message-ID: <CA+s+GJDMSvpY_0p05RfEh=P_uuLPGFezBiNY+e7aktbUt8-oyQ@mail.gmail.com> (raw)
In-Reply-To: <CANAnSg35RESWnodi01F0qyBY4RQm9TSmkKfp-6cWn2o36iRE5Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 701 bytes --]
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.
It really doesn't matter in what order the different places are updated, as
long as the news is propagated everywhere within a reasonable time-span of
say a day. Requiring a certain order would require unnecessary coordination.
Don't make problems where they don't exist, we have enough actual issues.
Wladimir
[-- Attachment #2: Type: text/html, Size: 1245 bytes --]
next prev parent reply other threads:[~2013-12-09 15:36 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 [this message]
2013-12-09 15:42 ` Drak
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='CA+s+GJDMSvpY_0p05RfEh=P_uuLPGFezBiNY+e7aktbUt8-oyQ@mail.gmail.com' \
--to=laanwj@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=drak@zikula.org \
/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