public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Wladimir <laanwj@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: [Bitcoin-development] Bitcoin Core 0.10.0rc4 tagged
Date: Thu, 5 Feb 2015 12:33:27 +0000	[thread overview]
Message-ID: <CA+s+GJBaQJPmCBKHLPfZ-_JjarpVCnAmz8eoD=Rg2HLx_vfn=A@mail.gmail.com> (raw)

FYI, I've just tagged v0.10rc4, and pushed my signatures to the
gitian.sigs repository.

Please start your gitian builders!

Changes relative to rc3:

- 1eb14af Increase block download timeout base from 10 to 20 minutes.
- 3916a81 Increase coverage of DERSIG edge cases
- 6da2028 Add RPC test for DERSIG BIP switchover logic
- 773c30d BIP66 changeover logic
- 18695f0 Example unit tests from BIP66
- abfbeaf Change IsDERSignature to BIP66 implementation
- b6347bf Fix priority calculation in CreateTransaction
- 2448d34 Avoid storing a reference passed to SignatureChecker constructors
- 1bbad80 Use separate SignatureChecker for CMutableTransaction
- 6a02ef8 [Qt] don't allow amount changes when AmountSpinBox is read-only
- b61940b Change Coin Control first column label
- c5044bc sleep-wait on genesis block during init with -reindex
- b24ff47 Make empty byte arrays pass CheckSignatureEncoding()
- ed4206a fix crash: CoinControl "space" bug
- 58259ad qt: fix broken unicode chars on osx 10.10
- aaf55d2 186a517 Add a -rpckeepalive option to disable RPC use of
HTTP persistent connections.

Hopefully this will be the last release candidate before the 0.10 final release.

Wladimir



             reply	other threads:[~2015-02-05 12:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-05 12:33 Wladimir [this message]
2015-02-06  9:54 ` [Bitcoin-development] Bitcoin Core 0.10.0rc4 tagged 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+GJBaQJPmCBKHLPfZ-_JjarpVCnAmz8eoD=Rg2HLx_vfn=A@mail.gmail.com' \
    --to=laanwj@gmail.com \
    --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