blob: 5f812f99c2b18df772ba42adf674e42158b9235a (
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
|
Return-Path: <luke@dashjr.org>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id C8EA2149B
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 30 Sep 2015 17:58:18 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from zinan.dashjr.org (zinan.dashjr.org [192.3.11.21])
by smtp1.linuxfoundation.org (Postfix) with ESMTP id 882DDFC
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 30 Sep 2015 17:58:18 +0000 (UTC)
Received: from ishibashi.localnet (unknown
[IPv6:2001:470:5:265:61b6:56a6:b03d:28d6])
(Authenticated sender: luke-jr)
by zinan.dashjr.org (Postfix) with ESMTPSA id 002121080196;
Wed, 30 Sep 2015 17:57:44 +0000 (UTC)
X-Hashcash: 1:25:150930:laanwj@gmail.com::B444g98fdDxMiQ91:aR+La
X-Hashcash: 1:25:150930:bitcoin-dev@lists.linuxfoundation.org::McIVvr1OAm=H3OCT:2mxd
From: Luke Dashjr <luke@dashjr.org>
To: "Wladimir J. van der Laan" <laanwj@gmail.com>
Date: Wed, 30 Sep 2015 17:57:42 +0000
User-Agent: KMail/1.13.7 (Linux/4.1.6-gentoo; KDE/4.14.8; x86_64; ; )
References: <20150924112555.GA21355@amethyst.visucore.com>
In-Reply-To: <20150924112555.GA21355@amethyst.visucore.com>
X-PGP-Key-Fingerprint: E463 A93F 5F31 17EE DE6C 7316 BD02 9424 21F4 889F
X-PGP-Key-ID: BD02942421F4889F
X-PGP-Keyserver: hkp://pgp.mit.edu
MIME-Version: 1.0
Content-Type: Text/Plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201509301757.44035.luke@dashjr.org>
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,T_RP_MATCHES_RCVD
autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Cc: Bitcoin development mailing list <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Bitcoin Core 0.12.0 release schedule
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Sep 2015 17:58:18 -0000
On Thursday, September 24, 2015 11:25:56 AM Wladimir J. van der Laan via
bitcoin-dev wrote:
> 2015-12-01
> -----------
> - Feature freeze
Where is "Consensus freeze"? Shouldn't this be put off until after the HK
workshop in case a hardfork is decided on? Or have we de-coupled it from the
release process entirely anyway (since old versions need an update for it
too)?
Luke
|
