From: Gavin Andresen <gavinandresen@gmail•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] Pulling for the 0.5 release
Date: Sat, 24 Sep 2011 11:19:40 -0400 [thread overview]
Message-ID: <CABsx9T3JZA4mujRgYRs6APaUtUjC+hkka34rZDq7PQFvz829xQ@mail.gmail.com> (raw)
Bright and early Monday morning I plan on pulling changes for the
Bitcoin 0.5 release into tip-of-git. Expect some tip-of-git chaos and
instability, I'm sure there will be issues to work through to move
from wxwidgets to qt for the GUI.
I'd like to have a release candidate ready in a week or two, giving
time for a week or two of testing, and have the 0.5 release available
a month from now, assuming no major show-stopper bugs or network
stability or denial-of-service or security vulnerabilities turn up
between now and then.
--
--
Gavin Andresen
reply other threads:[~2011-09-24 15: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=CABsx9T3JZA4mujRgYRs6APaUtUjC+hkka34rZDq7PQFvz829xQ@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