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
|
Return-Path: <laanwj@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 828741744
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 1 Oct 2015 08:51:03 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wi0-f175.google.com (mail-wi0-f175.google.com
[209.85.212.175])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id E626F24E
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 1 Oct 2015 08:51:02 +0000 (UTC)
Received: by wicfx3 with SMTP id fx3so22179046wic.1
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 01 Oct 2015 01:51:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=date:from:to:cc:subject:message-id:references:mime-version
:content-type:content-disposition:in-reply-to;
bh=LnFjZdyyKhpe9s9iDdKlKse6cBMEqyQKYk6tut75mPA=;
b=MeRKtDdmH7UA71bF2OA6QNA4sixx9keNxsr0TTZEa0WzWlZZee4gMSEb6UJwxRGZH1
QLhCN241G6KJ30pc3+etjXZMRLjiLIKyNtz8UMCOvG9g0yFv3xtL0suWOZzXVeUKU3zJ
Z+BYPVN1cf7MK9wLmDFMVwK2vozxBhboXbKEz6pSvQ9NueBSbknTGw9eOx/NSFUtTrBw
wK11JDZf14DE1Da+YztP4a14oAXchUV0qZMRwfhW+a4ZvFh+yWrX7o0o/ftn8+bbSCXl
0WDZU1qkhldWy2T0577xPMql8TM1bHhVBVblG5TfuaIFeTJro6SUaM4jV/9aQq3yqHeU
l8zg==
X-Received: by 10.180.103.35 with SMTP id ft3mr2145915wib.60.1443689461475;
Thu, 01 Oct 2015 01:51:01 -0700 (PDT)
Received: from amethyst.visucore.com (dhcp-089-098-228-253.chello.nl.
[89.98.228.253])
by smtp.gmail.com with ESMTPSA id q1sm4964790wje.39.2015.10.01.01.51.00
(version=TLS1_2 cipher=AES128-SHA256 bits=128/128);
Thu, 01 Oct 2015 01:51:01 -0700 (PDT)
Date: Thu, 1 Oct 2015 10:50:59 +0200
From: "Wladimir J. van der Laan" <laanwj@gmail.com>
To: Luke Dashjr <luke@dashjr.org>
Message-ID: <20151001085058.GA10010@amethyst.visucore.com>
References: <20150924112555.GA21355@amethyst.visucore.com>
<201509301757.44035.luke@dashjr.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <201509301757.44035.luke@dashjr.org>
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM,
RCVD_IN_DNSWL_LOW 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: Thu, 01 Oct 2015 08:51:03 -0000
On Wed, Sep 30, 2015 at 05:57:42PM +0000, Luke Dashjr wrote:
> 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)?
In principle, "feature freeze" means that any large code changes will no longer go into 0.12, unless fixing critical bugs.
I'm not keen on postponing 0.12 for such reasons - after the HK workshop I'm sure that it will take some development/testing/review before code makes it into anything. Apart from that there's a good point to decouple consensus changes from Bitcoin Core major releases.
We've seen lot of release date drift due to "this and this change needs to make it in" in the past, that was a major reason to switch to a time-based instead of feature-based release schedule.
We can always do a 0.12.1.
Wladimir
|
