From: Mike Hearn <mike@plan99•net>
To: Jeff Garzik <jgarzik@exmulti•com>
Cc: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin v0.3.24 release candidate available
Date: Fri, 8 Jul 2011 11:41:02 +0200 [thread overview]
Message-ID: <CANEZrP1CN5g-n16TfQoyuaX+1MGUnpm5fBKLwFiaeUWKGn0uaQ@mail.gmail.com> (raw)
In-Reply-To: <CA+8xBpcm2n4M=1KfqhaXPb-TQEeV5nk8sNkA8NZph3HcgPHKNA@mail.gmail.com>
A quick release would be good. The network is getting really sick:
http://forum.bitcoin.org/index.php?topic=26894.40
I brought up the latest rc3 on plan99.net.
Though it's not relevant for this release, there seems to be some kind
of shutdown issue. I did a "bitcoin stop" and then waited for the log
to indicate successful shutdown. But the parent process didn't quit,
leaving a zombie. I did a kill -9 on the parent to get rid of it, and
then the addr.dat file became corrupted. I had to remove it and the
"database" directory as running the db_recover command didn't work.
On Wed, Jul 6, 2011 at 10:05 PM, Jeff Garzik <jgarzik@exmulti•com> wrote:
> Bitcoin 0.3.24rc3 has been uploaded.
>
> Fixes appeared after -rc2 was tagged, so we just skipped straight to -rc3.
>
> Maybe final release on Friday?
>
> Changes since 0.3.24rc1:
>
> Gavin Andresen (2):
> Block-chain lock-in at 134444
> Do not use comma as thousands separator Using the comma as thousands s
>
> Matt Corallo (3):
> Added a couple minor things to match newer build process.
> Revert "Make UPnP default on Bitcoin but not on Bitcoind."
> Enable UPnP by default on bitcoin, but not on bitcoind (on gitian)
>
> Pieter Wuille (1):
> Fix synchronization of default key
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> dec9ff63fe6d0cffb2abc723281a4135c22f19ef bitcoin-0.3.24rc3-linux.tar.gz
> c171c6e5128d570d5d7d5a6896b672fcab778933 bitcoin-0.3.24rc3-src.tar.gz
> d4b5425eff673551a326d5326b92a06359dc1a3d bitcoin-0.3.24rc3-win32-setup.exe
> 0653302ac7f8b052d58667ae30da53c4f6230be5 bitcoin-0.3.24rc3-win32.zip
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (GNU/Linux)
>
> iQIVAwUBThS+Xdodwg8tvwyoAQINthAAqxOnungGYS1o7IB3D3M1NRPD/O/WNoB4
> ANIn+oZLYy5+0yZylckT/gbkPY3PkhsIE8hVqbxGDYaDzUpjwN+DLd+EMPg5/2vr
> Tp2b77Lzh6QszZzZhrs9LPLsB8Q/jzCAbbChAekkAAe4sGm0MFkxMEYaXE+RF/uj
> PX36hdtmWYMzeXwf3PtbI8rAE9ESwXVVF8B7/qFvDhy4lrbXaNnGb3hGyowrNVBM
> m1s4jyk/Lq5pPcoKlRN6kiujCbZBIy6VKgc74YaoMOrznHryoeYQVCg4tySfKkuG
> gfiZFEL6EwYeY8ipjcRBVLFGxbwzCbIhBcBO/Je2yC+EwAOplfyy+GBE3rXLuUkn
> AzMiL1i5nX6dNmkYqVE0+pbv81FeT+uc1i63CIjquLdVbxh3omdpYdYHs9q/zN/9
> geHU4WnpwwZhTFEclzZUOGo8IJ0wiNsTyQv9mwVEjoslnubXh4omqbW7Tpm7cXiP
> jlDZ42Ay+Z+AvafdLYP27vfjWJoMbjcu6qU2EXBOhmpkeaIcV43oEAd7suy0OLUq
> 8iNMpQHjlLnH0pcN8r38Tq+vuCuhPZtiPZd5dVKSF3PaCB6vAv8MulE0yhP2LEq3
> Q4MzxSlgGNEWCGIv19YfMnURxGMNMKB0cyQ8SMdLDR+IIB3NB5SreeG8c8P97s5p
> VnHOvTnpHyw=
> =vKTJ
> -----END PGP SIGNATURE-----
>
> --
> Jeff Garzik
> exMULTI, Inc.
> jgarzik@exmulti•com
>
> ------------------------------------------------------------------------------
> All of the data generated in your IT infrastructure is seriously valuable.
> Why? It contains a definitive record of application performance, security
> threats, fraudulent activity, and more. Splunk takes this data and makes
> sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-d2d-c2
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
prev parent reply other threads:[~2011-07-08 9:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-03 3:09 Jeff Garzik
2011-07-06 20:05 ` Jeff Garzik
2011-07-08 9:41 ` Mike Hearn [this message]
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=CANEZrP1CN5g-n16TfQoyuaX+1MGUnpm5fBKLwFiaeUWKGn0uaQ@mail.gmail.com \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=jgarzik@exmulti$(echo .)com \
/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