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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jgarzik@exmulti.com>) id 1TM1DJ-0001tz-Nx
for bitcoin-development@lists.sourceforge.net;
Wed, 10 Oct 2012 18:41:01 +0000
X-ACL-Warn:
Received: from mail-qa0-f54.google.com ([209.85.216.54])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1TM1DJ-0004QX-0o
for bitcoin-development@lists.sourceforge.net;
Wed, 10 Oct 2012 18:41:01 +0000
Received: by mail-qa0-f54.google.com with SMTP id y23so838107qad.13
for <bitcoin-development@lists.sourceforge.net>;
Wed, 10 Oct 2012 11:40:55 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=google.com; s=20120113;
h=mime-version:x-originating-ip:date:message-id:subject:from:to
:content-type:x-gm-message-state;
bh=KTl/Sf6hiFkS8b8IbB/5lGgW3kxRuSRpnfmm8/0/nnQ=;
b=AUoDSxEkpGKqhYmCoM6IM57hMscuCLA18h3avGeTcPfBzWpQySdk9prA+DUuTppi7e
a5pVhgMA6285zBoQhTw/+qseyNejC8Xk5XkfuSk1O2qzsPYA2BTvRx9b+5zacceRw9LY
/zHp/qIRqL/1/Shc5QeBmId/ObdVvJRtXfo633Blci12565DToh0dx5sUY5k4gX7Lahh
LVY8fWgpq2nkYHIplDIoQjq+tjEgDbo2erLTK6iIE1ImjgYfo6T4oPeeLKGK5cwdEfNk
UoywgDkcoO/iGvKvz7Fec/D0lh5SyB3H6Q1YXSXho8vSO2E4NjSRpDDaZtHpL0OTWmUT
gIog==
MIME-Version: 1.0
Received: by 10.49.96.162 with SMTP id dt2mr4077571qeb.48.1349894455523; Wed,
10 Oct 2012 11:40:55 -0700 (PDT)
Received: by 10.49.97.6 with HTTP; Wed, 10 Oct 2012 11:40:55 -0700 (PDT)
X-Originating-IP: [99.43.178.25]
Date: Wed, 10 Oct 2012 14:40:55 -0400
Message-ID: <CA+8xBpdLo+VoHiJNJWNn+NPHj9v33=bSXBhkBeoLr73z-qFrBQ@mail.gmail.com>
From: Jeff Garzik <jgarzik@exmulti.com>
To: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQmRqlDV2UlMO3V+UhUfXIZ4EQ0X4ZsWCFpO89CGUUJapxyA1Qn8Yb86KT879LzpOuivNmUn
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
X-Headers-End: 1TM1DJ-0004QX-0o
Subject: [Bitcoin-development] Post-0.7.1 tree freeze for ultraprune
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: Wed, 10 Oct 2012 18:41:01 -0000
Proposal: following 0.7.1 release, freeze the tree. Do not pull
anything, until ultraprune is pulled (or rejected, but I think the
latter is unlikely).
Common sense exceptions still apply (critical bug fixes, etc.)
Ultraprune does not need to be "perfect" to be pulled... this pull
would occur at the beginning of 0.8, leaving lots of room for
hammering out final details in-tree. The main hurdle is really
getting everyone to ACK the overall design and direction of the
ultraprune branch, especially Gavin.
Collecting those high-level design ACKs is more important to bitcoin
overall than even fine-grained code review; code mistakes can be fixed
in-tree during 0.8 development, once we all agree this is the correct
_design_. The real code mistakes and "sharp edges" will only be found
now with wide field testing.
For the record: yes, Design-ACK from me.
--
Jeff Garzik
exMULTI, Inc.
jgarzik@exmulti.com
|
