From: Wladimir <laanwj@gmail•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] Fwd: Bitcoin core 0.11 planning
Date: Mon, 11 May 2015 14:49:53 +0000 [thread overview]
Message-ID: <CA+s+GJCC=wQFnFnrukeDvt=dAncBTScBq84Vh_fCXnYc2Vq45g@mail.gmail.com> (raw)
In-Reply-To: <CA+s+GJBeZkWSKn4igC1ksynoQLfUpUtHBesq9MPi6yRqZZr4Gw@mail.gmail.com>
On Tue, Apr 28, 2015 at 11:01 AM, Pieter Wuille <pieter.wuille@gmail•com> wrote:
> As softforks almost certainly require backports to older releases and other
> software anyway, I don't think they should necessarily be bound to Bitcoin
> Core major releases. If they don't require large code changes, we can easily
> do them in minor releases too.
Agree here - there is no need to time consensus changes with a major
release, as they need to be ported back to older releases anyhow.
(I don't really classify them as software features, but properties of
the underlying system that we need to adopt to)
Wladimir
next prev parent reply other threads:[~2015-05-11 14:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 7:44 [Bitcoin-development] " Wladimir J. van der Laan
2015-04-28 10:49 ` Peter Todd
2015-04-28 11:01 ` Pieter Wuille
2015-04-28 13:42 ` Peter Todd
[not found] ` <CA+s+GJBeZkWSKn4igC1ksynoQLfUpUtHBesq9MPi6yRqZZr4Gw@mail.gmail.com>
2015-05-11 14:49 ` Wladimir [this message]
2015-05-11 15:00 ` Wladimir
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='CA+s+GJCC=wQFnFnrukeDvt=dAncBTScBq84Vh_fCXnYc2Vq45g@mail.gmail.com' \
--to=laanwj@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.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