From: "Luke-Jr" <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] State of Bitcoin Development: November Brain Dump
Date: Mon, 21 Nov 2011 20:11:46 -0500 [thread overview]
Message-ID: <201111212011.47683.luke@dashjr.org> (raw)
In-Reply-To: <CABsx9T2w7X1WJAMe6yuGcpZegb5G9Tjawt-Uk7d2RH7GAgoJaQ@mail.gmail.com>
On Monday, November 21, 2011 8:06:27 PM Gavin Andresen wrote:
> Finding the money to hire some professional QA people to help create
> test plans and then execute them (the test plans, not the QA people)
> is one possible answer.
Not prioritizing some unannounced "release schedule" over getting bugs fixed
before making the release is another part of the answer, at least.
prev parent reply other threads:[~2011-11-22 1:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-22 1:06 [Bitcoin-development] State of Bitcoin Development: November Brain Dump Gavin Andresen
2011-11-22 1:11 ` Luke-Jr [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=201111212011.47683.luke@dashjr.org \
--to=luke@dashjr.org \
--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