From: Drak <drak@zikula•org>
To: Gregory Maxwell <gmaxwell@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:19:05 +0000 [thread overview]
Message-ID: <CANAnSg35RESWnodi01F0qyBY4RQm9TSmkKfp-6cWn2o36iRE5Q@mail.gmail.com> (raw)
In-Reply-To: <CAAS2fgQCP+8-_pc00pHPDY_6-BO2gYKQ1nqnwwt_FUkZ0vNKfQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 862 bytes --]
On 9 December 2013 15:07, Gregory Maxwell <gmaxwell@gmail•com> wrote:
> On Mon, Dec 9, 2013 at 6:55 AM, Drak <drak@zikula•org> wrote:
> > It was released and it's all over bitcointalk/reddit
>
> It has not been released. It's queued for announcement. We were
> waiting for another independant gitian build before sending out the
> announcement.
>
Why would it be made available for download at sourceforge.net if it's not
actually released? The files are available here:
http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.8.6/ and
people watch the sf rss feeds etc...
Seems to me like there needs to be a better release workflow. As far as the
world is concerned, they are downloading the 0.8.6 and there is a lot of
community buzz about it already.
IMO, to avoid that, no files should be placed online unless they are the
official release.
Drak
[-- Attachment #2: Type: text/html, Size: 1604 bytes --]
next prev parent reply other threads:[~2013-12-09 15:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-06 6:52 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 [this message]
2013-12-09 15:25 ` Gregory Maxwell
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=CANAnSg35RESWnodi01F0qyBY4RQm9TSmkKfp-6cWn2o36iRE5Q@mail.gmail.com \
--to=drak@zikula$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=gmaxwell@gmail$(echo .)com \
/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