From: Arklan Uth Oslin <arklan.uthoslin@gmail•com>
To: Gavin Andresen <gavinandresen@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>,
bitcoin-test@lists•sourceforge.net
Subject: Re: [Bitcoin-development] [Bitcoin-test] Time for a 0.8.2 release
Date: Thu, 25 Apr 2013 06:45:19 -0600 [thread overview]
Message-ID: <CAGg41SVBveMSV=1+aQmHZLRht=Wuqhu4AnzDLsGj7zhzZKGH0A@mail.gmail.com> (raw)
In-Reply-To: <CABsx9T3ZYVosuL9MKpuK_5fJb01Yj-zBS0YGmdA-Jo4L3UHzhA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1885 bytes --]
unfortunately my winter has proven a complicated series of significant life
events - new work, etc - which sees me with little free time to help out.
sorry.
Arklan
----------
As long as there is light, the darkness holds no fear. And yet, even in the
deepest black, there is life. - Arklan Uth Oslin
I want to leave this world the same way I came into it: backwards and on
fire. - Arklan Uth Oslin
On Wed, Apr 24, 2013 at 9:22 AM, Gavin Andresen <gavinandresen@gmail•com>wrote:
> Consensus in #bitcoin-dev chat is that it is time to do a 0.8.2 release. A
> few important bugs have been fixed, and the goal will be to get a 0.8.2
> final release before the May 15'th hard fork deadline.
>
> Pieter has already started going through the issues list; help with
> testing, debugging, and fixing high-priority issues is very welcome. I'll
> also be going through the issues list and marking any issues I think need
> to be fixed with the '0.8.2' milestone.
>
> If translation work needs to be done, now is a great time to do it.
>
> We still don't have a basic QA checklist for testing of release
> candidates; I'll commit to spending a little of the remaining "Bitcoin
> Testing Project" bitcoins to whoever contributes to creating one.
>
> --
> --
> Gavin Andresen
>
>
> ------------------------------------------------------------------------------
> Try New Relic Now & We'll Send You this Cool Shirt
> New Relic is the only SaaS-based application performance monitoring service
> that delivers powerful full stack analytics. Optimize and monitor your
> browser, app, & servers with just a few lines of code. Try New Relic
> and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
> _______________________________________________
> Bitcoin-test mailing list
> Bitcoin-test@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-test
>
>
[-- Attachment #2: Type: text/html, Size: 2727 bytes --]
prev parent reply other threads:[~2013-04-25 12:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-24 15:22 [Bitcoin-development] " Gavin Andresen
2013-04-25 12:45 ` Arklan Uth Oslin [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='CAGg41SVBveMSV=1+aQmHZLRht=Wuqhu4AnzDLsGj7zhzZKGH0A@mail.gmail.com' \
--to=arklan.uthoslin@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=bitcoin-test@lists$(echo .)sourceforge.net \
--cc=gavinandresen@gmail$(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