From: Gavin Andresen <gavinandresen@gmail•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] Please help test 0.5 release candidate 1
Date: Mon, 10 Oct 2011 12:32:41 -0400 [thread overview]
Message-ID: <CABsx9T244BVwA2q5pBA4=9U=chsWvMUQ+s02NV62knrNoK1OgQ@mail.gmail.com> (raw)
Reposting from the forums:
https://bitcointalk.org/index.php?topic=47586
I just tagged the git tree "v0.5.0rc1". If you are able, please
compile and help test.
See the INSTALL file at the top of the source tree for instructions on
compiling. Binary releases for at least unix and mac should be
available in the next day or two (there is a show-stopper bug on
Windows, and we could use help from people familiar with
cross-compiling using mingw to update the Windows build process).
Major bugs you should be aware of:
Wallet does not relock on Win32
Major changes from version 0.4:
Switched from wxWidgets for the GUI to Qt, using Wladimir J. van der
Laan's bitcoin-qt. Why? We didn't have any wxWidgets programmers
contributing fixes or improvements.
New JSON-RPC commands:
getmemorypool : alternative to 'getwork' that provides everything
needed to construct a block with a custom generation transaction.
listsinceblock : Get all transactions in blocks since block [blockid]
signmessage/verifymessage : sign/verify a message with a wallet
public/private keypair
Deprecated JSON-RPC features:
'midstate' data item from getwork requests
Deprecated JSON-RPC commands that have been REMOVED:
setlabel
getlabel
getaddressesbylabel
getamountreceived
getallreceived
getreceivedbylabel
listreceivedbylabel
Run: git shortlog --no-merges v0.4.0..
... to get a complete list of changes, and thanks to everybody who is
contributing!
--
--
Gavin Andresen
next reply other threads:[~2011-10-10 16:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-10 16:32 Gavin Andresen [this message]
2011-10-10 21:54 ` Carlos Alberto Lopez Perez
2011-10-14 7:10 ` 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='CABsx9T244BVwA2q5pBA4=9U=chsWvMUQ+s02NV62knrNoK1OgQ@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