From: Gavin Andresen <gavinandresen@gmail•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] 0.7.1 release
Date: Wed, 3 Oct 2012 13:49:22 -0400 [thread overview]
Message-ID: <CABsx9T1v9Rfm_d7DcfbkkHEC96CwTNNp4_E1G97UBXqVHjVyOw@mail.gmail.com> (raw)
There is consensus that we need to do a 0.7.1 release to fix the
"click on a bitcoin: URI and nothing happens" bug on Windows.
I would really like to fix the "I upgraded from a binary running an
incompatible version of BDB and now I get a DB_RUNRECOVERY error on
startup" problem, too, and I've got a pull request that fixes half of
that problem (plus a bunch of other "my wallet is broken" cases):
"Handle corrupt wallets gracefully" :
https://github.com/bitcoin/bitcoin/pull/1895
This pull request:
"Add -reindex, to perform in-place reindexing of blockchain data
files" : https://github.com/bitcoin/bitcoin/pull/1870
... could be the basis for fixing the other half of the problem (if
blkindex.dat is bad, delete it and re-create it from the blk000?.dat
files).
Are there any other very-high-priority pull requests that should go
into a 0.7.1 release?
I'd like to pull:
"P2P: Do not request blocks from peers with fewer blocks than us" :
https://github.com/bitcoin/bitcoin/pull/1834
"In listaddressgroupings push down the IsMine check to run on each
input." : https://github.com/bitcoin/bitcoin/pull/1872
... and these which could be considered fixes to the new raw transactions API:
"Add redeemScript to raw transactions API" :
https://github.com/bitcoin/bitcoin/pull/1818
"Add new RPC "lockunspent", to prevent spending of selected outputs" :
https://github.com/bitcoin/bitcoin/pull/1861
--
--
Gavin Andresen
next reply other threads:[~2012-10-03 17:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-03 17:49 Gavin Andresen [this message]
2012-10-03 18:49 ` Wladimir
2012-10-03 19:53 ` Jeff Garzik
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=CABsx9T1v9Rfm_d7DcfbkkHEC96CwTNNp4_E1G97UBXqVHjVyOw@mail.gmail.com \
--to=gavinandresen@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