From: Gavin Andresen <gavinandresen@gmail.com>
To: Luke-Jr <luke@dashjr.org>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] 0.4.x stable branch
Date: Mon, 19 Sep 2011 08:49:08 -0400 [thread overview]
Message-ID: <CABsx9T2FBNv26E4LHmi9GVfi1HLR1wR__qGp1_gjco8rwN0L4Q@mail.gmail.com> (raw)
In-Reply-To: <201109181930.59565.luke@dashjr.org>
On Sun, Sep 18, 2011 at 7:30 PM, Luke-Jr <luke@dashjr.org> wrote:
> If we prepare the git repository + tags, would you guys be
> willing to make the actual release builds + source, and/or post such on the
> websites you administrate?
> Luke and various others in #bitcoin-stable
My initial reaction is no. Testing and bug-fixing is the bottleneck
for making core bitcoin better, and maintaining two release lines
won't make that better.
I also think that until we get to a "1.0" that we can all agree is
ready for everybody AND their grandma to use, using the word "stable"
would be dishonest.
Would we link to your binaries if you want to create 0.4.* releases,
build binaries, then QA test and release them?
I dunno-- what do other people think?
Eventually, when there are a bunch of bitcoin implementations to
choose from, I think bitcoin.org should look like bittorrent.org -- it
should become a forum for developers to exchange ideas about the
direction of bitcoin.
--
--
Gavin Andresen
next prev parent reply other threads:[~2011-09-19 12:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-18 23:30 [Bitcoin-development] 0.4.x stable branch Luke-Jr
2011-09-19 12:49 ` Gavin Andresen [this message]
2011-09-19 13:03 ` Gregory Maxwell
2011-09-19 13:48 ` Amir Taaki
2011-09-19 15:00 ` Luke-Jr
2011-09-19 15:06 ` Gregory Maxwell
2011-09-20 4:41 ` theymos
2011-09-20 19:10 ` Jeff Garzik
2011-09-20 20:37 ` Luke-Jr
2011-09-21 14:24 ` Alex Waters
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=CABsx9T2FBNv26E4LHmi9GVfi1HLR1wR__qGp1_gjco8rwN0L4Q@mail.gmail.com \
--to=gavinandresen@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=luke@dashjr.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