public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Gavin Andresen <gavinandresen@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: [Bitcoin-development] Version 0.6 release candidate 1 plan
Date: Mon, 6 Feb 2012 10:44:09 -0500	[thread overview]
Message-ID: <CABsx9T0-eMkfJiOL_2VN5TUuvs_fYANa3XXoM5OX4AMP1W2iSA@mail.gmail.com> (raw)

There are several major changes in git HEAD that are ready for wider
testing. The best way of getting lots of testing is to release
binaries, so I'm going to be pulling together a release candidate in
the next day or two.

The goal will be to get at least a full month of release candidate
review/testing before releasing a 0.6 final, with zero High Priority
bugs ( https://github.com/bitcoin/bitcoin/issues?labels=Priority+High&state=open
)

Here's the proposed TODO list for a rc1:

Pull:
800 : bug fix, multiple output display fix in GUI
799 : Have bitcoind recomend a secure RPC password
769 : Make transactions with extra data in scriptSig non-standard

Rebase/pull:
795 : Fix minimize to tray

Pull a modified version of:
755 : Don't vote for /P2SH/ unless -p2sh specified

I'd like to pull 787 (CAddrMan: stochastic address manager) but it
didn't pass my sanity tests.

I'm going to start a separate discussion thread with some thoughts on
rolling out higher-level multisignature support.

-- 
--
Gavin Andresen



             reply	other threads:[~2012-02-06 15:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-06 15:44 Gavin Andresen [this message]
2012-02-06 15:54 ` [Bitcoin-development] Version 0.6 release candidate 1 plan Luke-Jr
2012-02-07 15:04   ` Luke-Jr
2012-02-07 16:14     ` Luke-Jr
2012-02-07 16:14     ` Gavin Andresen

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=CABsx9T0-eMkfJiOL_2VN5TUuvs_fYANa3XXoM5OX4AMP1W2iSA@mail.gmail.com \
    --to=gavinandresen@gmail.com \
    --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