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 4095D207C for ; Wed, 30 Sep 2015 18:10:33 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-wi0-f173.google.com (mail-wi0-f173.google.com [209.85.212.173]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 0B3EC298 for ; Wed, 30 Sep 2015 18:10:31 +0000 (UTC) Received: by wicfx3 with SMTP id fx3so74016826wic.0 for ; Wed, 30 Sep 2015 11:10:30 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=oPx9nPjG6JV737gbEhB14Avr9oSOd3wkMkABUhrZ9EI=; b=FdvTEEk+nCAE3PMlvoqzM0QFEHBvWjitntX8POINp79X8UhRJ7kntWhqXgQCnOBXlA 5N9H3Ct6x7AiiDeUEgzE0pEO2Lp3qAFIQqHyg8bigzW5Hio9OpibDXUryDmWFEWlHWpZ ccVjpAlclWblHWrl5Yc7Q9caJ5voZZRdiVaNIM44RRVBDEMKcyLKlLbhJYCwNW8wkAWl 8aFLiUtKUdEjrJC+37ZnaXn+u647unS1aNomI39DNzMeRWC6uwOuQeWZyISuhuqB2fj9 NUpzyme5K10vCSj3bb6eAwF3092yOJAXGdUAFTCWWJKFj3e5ix82JO20ks0pMy/kMECn FQyA== X-Gm-Message-State: ALoCoQmCn7gAlrfytx0zMQD5cIyn0jU97PeYTeoKKg7OrlbMd5y+QRDvmDrCVOz1FzokiUu2mlbW MIME-Version: 1.0 X-Received: by 10.180.107.130 with SMTP id hc2mr30662363wib.92.1443636630811; Wed, 30 Sep 2015 11:10:30 -0700 (PDT) Received: by 10.194.114.199 with HTTP; Wed, 30 Sep 2015 11:10:30 -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 20:10:30 +0200 Message-ID: From: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= To: Luke Dashjr Content-Type: text/plain; charset=UTF-8 X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,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 18:10:33 -0000 Yes, I believe consensus rule changes don't need to be couple with major releases, there's no problem that I can see in them being minor releases if they're not ready on time for a major release. On Wed, Sep 30, 2015 at 7:57 PM, Luke Dashjr via bitcoin-dev 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