From: Melvin Carvalho <melvincarvalho@gmail•com>
To: Luke-Jr <luke@dashjr•org>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] (no subject)
Date: Sat, 25 May 2013 11:23:12 +0200 [thread overview]
Message-ID: <CAKaEYhJycyXjEBa26PJrNdBWEeTUqW+HKEvvjTi-R4PTOSy85w@mail.gmail.com> (raw)
In-Reply-To: <201305250853.19603.luke@dashjr.org>
[-- Attachment #1: Type: text/plain, Size: 1471 bytes --]
On 25 May 2013 10:53, Luke-Jr <luke@dashjr•org> wrote:
> On Saturday, May 25, 2013 8:25:35 AM Melvin Carvalho wrote:
> > It might be an idea to have 'rule change' fixes and 'bug fix' releases go
> > out separately
>
> Bitcoin is a consensus system. You can't run clients with different rules
> on
> the same blockchain/network - it just won't work! Maybe we're now talking
> about mere client default policies? In which case, you should be able to
> configure previous behaviour...
>
[[ Not wishing to stray too far off topic ]]
I think you are perhaps underestimating the effect of 'mere' default
policies.
It would be nice to think that every node was a free thinking individual
that is motivated to vote with their feet, but in practice most people dont
have time.
There is research showing that 80% of users tend to accept defaults.
Rule changes and changing defaults would seem to be things worth weighing.
Bug fixes hopefully should be fairly unanimous. Of course a grey area
exists in between.
>
> If you want just bug fixes and rule changes, without policy default
> changes,
> new features, etc, you can use the 0.4.x - 0.7.x backports. But be advised
> these are short-term solutions and won't be maintained forever - so you
> really
> should try to get the behaviour you want from the current release. If you
> can't for some reason, please do report a bug explaining what it is the
> older
> version was capable of that the new one isn't!
>
> Luke
>
[-- Attachment #2: Type: text/html, Size: 2189 bytes --]
next prev parent reply other threads:[~2013-05-25 9:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-25 5:46 Zooko Wilcox-OHearn
2013-05-25 8:09 ` Wladimir
2013-05-27 2:43 ` [Bitcoin-development] Handling alerts & communication on bitcoin.org Saïvann
2013-05-25 8:25 ` [Bitcoin-development] (no subject) Melvin Carvalho
2013-05-25 8:53 ` Luke-Jr
2013-05-25 9:23 ` Melvin Carvalho [this message]
2014-05-04 1:47 losewife
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=CAKaEYhJycyXjEBa26PJrNdBWEeTUqW+HKEvvjTi-R4PTOSy85w@mail.gmail.com \
--to=melvincarvalho@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=luke@dashjr$(echo .)org \
/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