From: Gregory Maxwell <gmaxwell@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 11:06:07 -0400 [thread overview]
Message-ID: <CAAS2fgSKJcHRnO3eHG33rqE9kRS2uGpWAxO_xLNVSYQ_BigveQ@mail.gmail.com> (raw)
In-Reply-To: <201109191100.58100.luke@dashjr.org>
On Mon, Sep 19, 2011 at 11:00 AM, Luke-Jr <luke@dashjr.org> wrote:
> The problem with the current development model is that bugfixes are done
> alongside improvements, and code changes *always* have the potential to
> introduce new bugs, no matter how careful anyone is. So to stay on top of
> bugfixes right now implies risking new bugs being introduced. What good is
> getting one bug fixed, if it comes with 20 new yet-to-be-discovered bugs?
Bug fixes also introduce bugs. Considering the fairly small number of new
features added, I'd take a bet that most of the more recently introduced
bugs were the result of fixes not features.
next prev parent reply other threads:[~2011-09-19 15:06 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
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 [this message]
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=CAAS2fgSKJcHRnO3eHG33rqE9kRS2uGpWAxO_xLNVSYQ_BigveQ@mail.gmail.com \
--to=gmaxwell@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