summaryrefslogtreecommitdiff
path: root/5e/6235032da9545274c1d77e58ad45876c74f4fc
blob: 095436dc42c9b95b8780c492f3fd660e9898806a (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <luke@dashjr.org>) id 1RuQtt-0004Xk-NK
	for bitcoin-development@lists.sourceforge.net;
	Mon, 06 Feb 2012 15:54:41 +0000
X-ACL-Warn: 
Received: from zinan.dashjr.org ([173.242.112.54])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
	id 1RuQtp-00060B-Po for bitcoin-development@lists.sourceforge.net;
	Mon, 06 Feb 2012 15:54:41 +0000
Received: from ishibashi.localnet (fl-184-4-164-217.dhcp.embarqhsd.net
	[184.4.164.217]) (Authenticated sender: luke-jr)
	by zinan.dashjr.org (Postfix) with ESMTPSA id 36A6056062D;
	Mon,  6 Feb 2012 15:54:30 +0000 (UTC)
From: "Luke-Jr" <luke@dashjr.org>
To: Gavin Andresen <gavinandresen@gmail.com>
Date: Mon, 6 Feb 2012 10:54:25 -0500
User-Agent: KMail/1.13.7 (Linux/3.2.2-gentoo; KDE/4.7.4; x86_64; ; )
References: <CABsx9T0-eMkfJiOL_2VN5TUuvs_fYANa3XXoM5OX4AMP1W2iSA@mail.gmail.com>
In-Reply-To: <CABsx9T0-eMkfJiOL_2VN5TUuvs_fYANa3XXoM5OX4AMP1W2iSA@mail.gmail.com>
X-PGP-Key-Fingerprint: CE5A D56A 36CC 69FA E7D2 3558 665F C11D D53E 9583
X-PGP-Key-ID: 665FC11DD53E9583
X-PGP-Keyserver: x-hkp://subkeys.pgp.net
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201202061054.26448.luke@dashjr.org>
X-Spam-Score: -0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay
	domain
X-Headers-End: 1RuQtp-00060B-Po
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Version 0.6 release candidate 1 plan
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Mon, 06 Feb 2012 15:54:41 -0000

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