public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@gmail.com>
To: Luke Dashjr <luke@dashjr.org>
Cc: Bitcoin development mailing list <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Bitcoin Core 0.12.0 release schedule
Date: Wed, 30 Sep 2015 15:24:29 -0400	[thread overview]
Message-ID: <CADm_WcYXCiACgYWhsp-ccCGk_UQT1aETaJD7-UV+tiLADS7sgg@mail.gmail.com> (raw)
In-Reply-To: <201509301757.44035.luke@dashjr.org>

[-- Attachment #1: Type: text/plain, Size: 772 bytes --]

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
>

[-- Attachment #2: Type: text/html, Size: 1405 bytes --]

  parent reply	other threads:[~2015-09-30 19:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-24 11:25 [bitcoin-dev] Bitcoin Core 0.12.0 release schedule Wladimir J. van der Laan
2015-09-29 21:22 ` Jeff Garzik
2015-09-30 17:57 ` Luke Dashjr
2015-09-30 18:10   ` Jorge Timón
2015-09-30 19:24   ` Jeff Garzik [this message]
2015-10-01  8:50   ` Wladimir J. van der Laan
2015-10-01  9:05     ` Marcel Jamin
2015-10-01  9:17       ` Btc Drak
     [not found]         ` <CAAUq484+g89yD+s7iR_mGWPM3TTN7V6-EPb1ig=P1BKfcbztPg@mail.gmail.com>
2015-10-01  9:41           ` [bitcoin-dev] Fwd: " Marcel Jamin
2015-10-01  9:56             ` Wladimir J. van der Laan
2015-10-01 10:10               ` Marcel Jamin
2015-10-01 10:15                 ` Wladimir J. van der Laan
2015-10-01 10:34                   ` Marcel Jamin
2015-10-01 10:50             ` Jeff Garzik
2015-10-01 20:20             ` Luke Dashjr

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CADm_WcYXCiACgYWhsp-ccCGk_UQT1aETaJD7-UV+tiLADS7sgg@mail.gmail.com \
    --to=jgarzik@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=luke@dashjr.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox