From: Matt Corallo <bitcoin-list@bluematt.me>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Project status
Date: Mon, 29 Aug 2011 21:09:03 -0400 [thread overview]
Message-ID: <1314666543.5889.2.camel@BMThinkPad.lan.bluematt.me> (raw)
In-Reply-To: <CABsx9T20JDnt5xF24HbJdhHe=MFZ3PDyk2cE+Q4V8iC0rgbASg@mail.gmail.com>
On Mon, 2011-08-29 at 16:10 -0400, Gavin Andresen wrote:
> Quick brain dump on a bunch of stuff:
>
> I'd like to get a 0.4 release out, but am still working on a fix for
> the deadlock bugs that the new wallet encryption and/or the CWallet
> refactoring caused. My short-term plan is to reduce the number of
> locks and make sure they're always acquired in a consistent order.
> Longer term, I think reworking the design to be based on
> boost::asio and use fewer threads is probably the right thing to do.
Hopefully working on something that would help do this now.
>
> Other things on the 0.4 TODO list: block chain checkpoint (got a PULL
> for that, thanks). Updated list of hard-coded seed nodes (nanotube
> did that last time). Pieter's dump/import privkey patch.
Also my build update pull would be much appreciated.
>
> After my talk at the conference, Alex Waters approached me about being
> the core bitcoin Q/A lead; he'll be working on creating test plans,
> keeping on top of the issues list, testing new features, and
> suggesting improvements to the code/test/release process. And
> whatever else he thinks needs to be done to improve core bitcoin.
NICE
next prev parent reply other threads:[~2011-08-30 1:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-29 20:10 [Bitcoin-development] Project status Gavin Andresen
2011-08-29 20:15 ` Luke-Jr
2011-08-30 1:09 ` Matt Corallo [this message]
2011-09-13 14:43 Gavin Andresen
2011-09-13 16:40 ` Luke-Jr
2011-09-13 16:48 ` Douglas Huff
2011-09-13 16:53 ` Luke-Jr
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=1314666543.5889.2.camel@BMThinkPad.lan.bluematt.me \
--to=bitcoin-list@bluematt.me \
--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