From: Matt Corallo <bitcoin-list@bluematt.me>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] 0.3.24
Date: Sun, 03 Jul 2011 03:58:40 +0200 [thread overview]
Message-ID: <1309658320.10530.82.camel@Desktop666> (raw)
In-Reply-To: <BANLkTim30QSJcV=kqfr=hby4Q9RaoyFREw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1208 bytes --]
Sorry this took so long, I got distracted...
Anyway 0.3.24 RC1 builds available at
http://dl.dropbox.com/u/29653426/Bitcoin%200.3.24%20RC1.tar.bz2
SHA1:
bb829e037aef86c5d9da384c0ff3c91ce8b11d5a Bitcoin 0.3.24 RC1.tar.bz2
Builds gitian signed and email signed as always.
Notes:
Couple things need fixed up before release wrt build engineering:
http://forum.bitcoin.org/index.php?topic=24841.0 (still haven't had a
chance to dig up a copy of Win98 and spin up a VM to test any results of
this one).
Build on Ubuntu 8.04 instead of 10.04 so that oder libcs can work (and
do thorough testing of that resulting binary on newer libcs specifically
openSUSE 11.04, see http://forum.bitcoin.org/index.php?topic=21767.0 )
Sorry to hold up release on this crap that is still unfixed after
0.3.21...
Matt
On Sat, 2011-07-02 at 17:07 -0400, Jeff Garzik wrote:
> On Fri, Jul 1, 2011 at 10:05 PM, Gavin Andresen <gavinandresen@gmail.com> wrote:
> > I think we should move forwards, not sideways-- git tip + whatever we
> > need to fix bugs in current tip is my preference.
> >
> > RE: upnp: I say pull Matt's patch (bitcoin=upnp, bitcoind=!upnp).
>
> Just tagged v0.3.24rc1...
>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2011-07-03 1:59 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-01 0:07 [Bitcoin-development] 0.3.24 Matt Corallo
2011-07-01 2:07 ` Gregory Maxwell
2011-07-01 2:44 ` Douglas Huff
2011-07-01 12:41 ` Douglas Huff
2011-07-01 8:00 ` Pieter Wuille
2011-07-01 8:39 ` Jeff Garzik
2011-07-01 12:31 ` Gavin Andresen
2011-07-01 12:40 ` Matt Corallo
2011-07-01 15:06 ` Gavin Andresen
2011-07-01 16:35 ` jan
2011-07-01 16:47 ` Robert McKay
2011-07-01 17:47 ` Douglas Huff
2011-07-01 17:50 ` Matt Corallo
2011-07-01 17:52 ` Douglas Huff
2011-07-01 22:03 ` Matt Corallo
2011-07-01 22:07 ` Douglas Huff
2011-07-01 17:59 ` Gregory Maxwell
2011-07-01 23:42 ` Jeff Garzik
2011-07-02 0:37 ` Jeff Garzik
2011-07-02 0:46 ` Matt Corallo
2011-07-02 0:51 ` Gregory Maxwell
2011-07-02 1:05 ` Douglas Huff
2011-07-02 1:12 ` Matt Corallo
2011-07-02 2:05 ` Gavin Andresen
2011-07-02 21:07 ` Jeff Garzik
2011-07-03 1:58 ` Matt Corallo [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=1309658320.10530.82.camel@Desktop666 \
--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