From: Luke Dashjr <luke@dashjr•org>
To: bitcoin-dev@lists•linuxfoundation.org, Marcel Jamin <marcel@jamin•net>
Subject: Re: [bitcoin-dev] Fwd: Bitcoin Core 0.12.0 release schedule
Date: Thu, 1 Oct 2015 20:20:22 +0000 [thread overview]
Message-ID: <201510012020.23821.luke@dashjr.org> (raw)
In-Reply-To: <CAAUq4861Wd2c42gVy7SoW9414R8RGY+Yzp7rDtzagrwQewnFWg@mail.gmail.com>
On Thursday, October 01, 2015 9:41:25 AM Marcel Jamin via bitcoin-dev wrote:
> I guess the question then becomes why bitcoin still is <1.0.0
>
> I'd say it's safe to say that it's used in production.
But it's not *ready* to be used in production. :(
For 1.0, I would expect:
libbitcoinconsensus: an API that makes implementing a full node practical.
Bitcoin Core GUI: reasonably usable safely by non-technical people.
Bitcoin Core Daemon: a reasonably safe wallet (currently blocked by backup-
resistant accounting system)
Luke
prev parent reply other threads:[~2015-10-01 20:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-24 11:25 [bitcoin-dev] " Wladimir J. van der Laan
2015-09-29 21:22 ` Jeff Garzik
2015-09-30 17:57 ` Luke Dashjr
2015-09-30 18:10 ` Jorge Timón
2015-09-30 19:24 ` Jeff Garzik
2015-10-01 8:50 ` Wladimir J. van der Laan
2015-10-01 9:05 ` Marcel Jamin
2015-10-01 9:17 ` Btc Drak
[not found] ` <CAAUq484+g89yD+s7iR_mGWPM3TTN7V6-EPb1ig=P1BKfcbztPg@mail.gmail.com>
2015-10-01 9:41 ` [bitcoin-dev] Fwd: " Marcel Jamin
2015-10-01 9:56 ` Wladimir J. van der Laan
2015-10-01 10:10 ` Marcel Jamin
2015-10-01 10:15 ` Wladimir J. van der Laan
2015-10-01 10:34 ` Marcel Jamin
2015-10-01 10:50 ` Jeff Garzik
2015-10-01 20:20 ` Luke Dashjr [this message]
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=201510012020.23821.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=marcel@jamin$(echo .)net \
/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