From: Gregory Maxwell <gmaxwell@gmail•com>
To: Gavin Andresen <gavinandresen@gmail•com>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] 0.4.x stable branch
Date: Mon, 19 Sep 2011 09:03:39 -0400 [thread overview]
Message-ID: <CAAS2fgQ-GZ+veHEKayw4qQuBHYXZcQruEw1iUwdyEtdom3OVmA@mail.gmail.com> (raw)
In-Reply-To: <CABsx9T2FBNv26E4LHmi9GVfi1HLR1wR__qGp1_gjco8rwN0L4Q@mail.gmail.com>
On Mon, Sep 19, 2011 at 8:49 AM, Gavin Andresen <gavinandresen@gmail•com> wrote:
> 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.
I think the primary concern that they are attempting to address there
is providing a stable base bitcoind for miners, banks, and webservices
to apply their patches on top of.
Right now, if they want to keep up with development they are stuck
forward porting against often disruptive changes as just about
everyone running something of importance needs some patch or another
so you have people who are clearly in the know like Luke and tcatm
trailing development on some of their systems by many months.
This isn't healthy for the network.
I'm not convinced a bugfixes only branch will help much: Even bug fixes
will disrupt local fixes, and testing and supervising your upgrade usually
takes more effort than the forward porting.
I'd rather see more effort put into mainlining the changes people are
carrying sooner and restructuring code to better accommodate patches
which aren't suitable for mainline. This will also encourage people
to make the fixes they're running publicly available, rather than
just keeping them private for competitive advantage.
next prev parent reply other threads:[~2011-09-19 13:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-18 23:30 Luke-Jr
2011-09-19 12:49 ` Gavin Andresen
2011-09-19 13:03 ` Gregory Maxwell [this message]
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=CAAS2fgQ-GZ+veHEKayw4qQuBHYXZcQruEw1iUwdyEtdom3OVmA@mail.gmail.com \
--to=gmaxwell@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=gavinandresen@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