From: Gregory Maxwell <gmaxwell@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 07:25:25 -0800 [thread overview]
Message-ID: <CAAS2fgSL9ptEmW-zkHm-Yzfm3FCNNMtXMc54Epj76DuuyNFS7w@mail.gmail.com> (raw)
In-Reply-To: <CANAnSg35RESWnodi01F0qyBY4RQm9TSmkKfp-6cWn2o36iRE5Q@mail.gmail.com>
On Mon, Dec 9, 2013 at 7:19 AM, Drak <drak@zikula.org> wrote:
> Why would it be made available for download at sourceforge.net if it's not
> actually released? The files are available here:
Because it takes time to put the files up, propagate to mirrors, check
by multiple people that the downloads work an the signatures pass.
Every release comes with a release announcement, you'll know its out
when you see the release announcement.
The alternative is that announcements go out and the files are not
correct, or hide the files in the release pipeline and allow less
public participation in the release workflow. I think that would be
unfortunate.
next prev parent reply other threads:[~2013-12-09 15:25 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 [this message]
2013-12-09 15:35 ` Wladimir
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=CAAS2fgSL9ptEmW-zkHm-Yzfm3FCNNMtXMc54Epj76DuuyNFS7w@mail.gmail.com \
--to=gmaxwell@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