public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "Luke-Jr" <luke@dashjr.org>
To: Gavin Andresen <gavinandresen@gmail.com>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Version 0.6 release candidate 1 plan
Date: Mon, 6 Feb 2012 10:54:25 -0500	[thread overview]
Message-ID: <201202061054.26448.luke@dashjr.org> (raw)
In-Reply-To: <CABsx9T0-eMkfJiOL_2VN5TUuvs_fYANa3XXoM5OX4AMP1W2iSA@mail.gmail.com>

On Monday, February 06, 2012 10:44:09 AM Gavin Andresen wrote:
> 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.

There are still many other pull requests that seem to be ready, but perhaps 
those can just as well wait for 0.7 if the 0.6 changes are deemed too much to 
add onto. Here are some that seem to be well-tested, and have been part of 
next-test for a while:
	719 coinbaser (already verbally accepted by Gavin for 0.6 a while ago!)
	568 rpc_keepalive
	565 optimize_FastGetWork
	715 bugfix_client_name
	562 optimize_ToHex

> 769 : Make transactions with extra data in scriptSig non-standard

If this affects relaying, it will significantly harm the ability to replace 
the current spammy "green address" scheme with a sensible extra signature 
system. On the miner end, it could significantly harm adoption of such a 
system.

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

What else do I need to change for this?

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

I can also confirm I have seen at least one addr.db corruption with this.

Luke



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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-06 15:44 [Bitcoin-development] Version 0.6 release candidate 1 plan Gavin Andresen
2012-02-06 15:54 ` Luke-Jr [this message]
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=201202061054.26448.luke@dashjr.org \
    --to=luke@dashjr.org \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=gavinandresen@gmail.com \
    /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