public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "Luke-Jr" <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] (no subject)
Date: Sat, 25 May 2013 08:53:17 +0000	[thread overview]
Message-ID: <201305250853.19603.luke@dashjr.org> (raw)
In-Reply-To: <CAKaEYhKOmSc+Mz=vA-M=34aXOs=VfC0jvCP+qNSdjE_2WVUfkg@mail.gmail.com>

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...

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



  reply	other threads:[~2013-05-25  9:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-25  5:46 [Bitcoin-development] (no subject) 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 [this message]
2013-05-25  9:23     ` Melvin Carvalho
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=201305250853.19603.luke@dashjr.org \
    --to=luke@dashjr.org \
    --cc=bitcoin-development@lists.sourceforge.net \
    /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