From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 4D4D410C4 for ; 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 ; Wed, 30 Sep 2015 19:24:31 +0000 (UTC) Received: by wicfx3 with SMTP id fx3so76669566wic.0 for ; 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: From: Jeff Garzik To: Luke Dashjr 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 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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
Right; In general, the consensus is to decouple from Bitco= in Core releases.


On Wed, Sep 30, 2015 at 1:57 PM, Luke Dashjr via bitco= in-dev <bitcoin-dev@lists.linuxfoundation.org><= /span> 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 th= e
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/mail= man/listinfo/bitcoin-dev

--f46d044481af2864380520fbe1f2--