From: Gavin Andresen <gavinandresen@gmail•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] 0.8.4 release candidate 2 : please help test
Date: Thu, 22 Aug 2013 08:19:39 +1000 [thread overview]
Message-ID: <CABsx9T0xz+fhb1UmG=T-5PMMRWGN84RK40FsTR=1XuWcuXO6=Q@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 839 bytes --]
0.8.4 release candidate 2 is available at:
https://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.8.4/test/
This is a maintenance release to fix a critical bug and fix three minor
security issues; it contains very few changes from the 0.8.3 release.
The two changes that need testing:
1) OSX FD_FULLSYNC leveldb corruption fix. If you have had trouble with
database corruption on OSX, please try this release and let us know if it
seems to help. Also let us know if you experience any performance problems
with this release.
2) Bloom filter optimization. If you have code that uses the bloom-filtered
block (merkleblock) protocol, please try it against this release and let us
know if you run into any issues.
PS: a critical last-minute bug was found in release candidate 1; it was
never released.
--
--
Gavin Andresen
[-- Attachment #2: Type: text/html, Size: 1143 bytes --]
reply other threads:[~2013-08-21 22:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CABsx9T0xz+fhb1UmG=T-5PMMRWGN84RK40FsTR=1XuWcuXO6=Q@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