Return-Path: <jgarzik@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 4D4D410C4
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 30 Sep 2015 19:24:32 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wi0-f179.google.com (mail-wi0-f179.google.com
	[209.85.212.179])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 85125163
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 30 Sep 2015 19:24:31 +0000 (UTC)
Received: by wicfx3 with SMTP id fx3so76669566wic.0
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 30 Sep 2015 12:24:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=uIYry09zqvhaRw/zC3KFXS3xSDVz7Zpx0qOMhvjT13M=;
	b=V2b0PHkdyrzNaBtpJoLvKe0p7SGBfHM5KJ1pAYt2cHzFvg9AvC2Ex9cH9Ap1ibx5MR
	9ZC0nlKs9GE5hm6a35aizsVWp7gDhCs/wjKCgnPqR73EXMSvxmSeJRoGhDWdC6GoPG17
	mkwqYdAgNqbXKTYQXT00UeseQvZilJ8sPSQFfRJC4juMFCWngRgUjt8vGnxLgYE9yuuT
	7t9Tca7NbgNVFB86nzc2dZSfQHRbjzZKk5QzRcNi38vqBlUXCQDJSeUHWWqgQ211SWoc
	6inTqC+ajoxmxacVOQlVH4N5qotKI3I1EWdTPx8apzuRTK7RPr1lBbT83iRzhdjxP4Gy
	6L5A==
MIME-Version: 1.0
X-Received: by 10.180.87.1 with SMTP id t1mr6466169wiz.33.1443641069952; Wed,
	30 Sep 2015 12:24:29 -0700 (PDT)
Received: by 10.28.158.9 with HTTP; Wed, 30 Sep 2015 12:24:29 -0700 (PDT)
In-Reply-To: <201509301757.44035.luke@dashjr.org>
References: <20150924112555.GA21355@amethyst.visucore.com>
	<201509301757.44035.luke@dashjr.org>
Date: Wed, 30 Sep 2015 15:24:29 -0400
Message-ID: <CADm_WcYXCiACgYWhsp-ccCGk_UQT1aETaJD7-UV+tiLADS7sgg@mail.gmail.com>
From: Jeff Garzik <jgarzik@gmail.com>
To: Luke Dashjr <luke@dashjr.org>
Content-Type: multipart/alternative; boundary=f46d044481af2864380520fbe1f2
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,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: Wed, 30 Sep 2015 19:24:32 -0000

--f46d044481af2864380520fbe1f2
Content-Type: text/plain; charset=UTF-8

Right; In general, the consensus is to decouple from Bitcoin Core releases.


On Wed, Sep 30, 2015 at 1:57 PM, Luke Dashjr via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> 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)?
>
> Luke
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

--f46d044481af2864380520fbe1f2
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Right; In general, the consensus is to decouple from Bitco=
in Core releases.<div><br></div></div><div class=3D"gmail_extra"><br><div c=
lass=3D"gmail_quote">On Wed, Sep 30, 2015 at 1:57 PM, Luke Dashjr via bitco=
in-dev <span dir=3D"ltr">&lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfound=
ation.org" target=3D"_blank">bitcoin-dev@lists.linuxfoundation.org</a>&gt;<=
/span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex">On Thursday, September 24, =
2015 11:25:56 AM Wladimir J. van der Laan via<br>
<span class=3D"">bitcoin-dev wrote:<br>
&gt; 2015-12-01<br>
&gt; -----------<br>
&gt; - Feature freeze<br>
<br>
</span>Where is &quot;Consensus freeze&quot;? Shouldn&#39;t this be put off=
 until after the HK<br>
workshop in case a hardfork is decided on? Or have we de-coupled it from th=
e<br>
release process entirely anyway (since old versions need an update for it<b=
r>
too)?<br>
<br>
Luke<br>
<div class=3D"HOEnZb"><div class=3D"h5">___________________________________=
____________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.=
linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
</div></div></blockquote></div><br></div>

--f46d044481af2864380520fbe1f2--