From: Jeff Garzik <jgarzik@gmail.com>
To: "Wladimir J. van der Laan" <laanwj@gmail.com>
Cc: Bitcoin development mailing list <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Bitcoin Core 0.12.0 release schedule
Date: Tue, 29 Sep 2015 17:22:58 -0400 [thread overview]
Message-ID: <CADm_WcY9Qd7OKJTr_H0YUVo4PAkV2tKrjQ-0-iTV5ogNrQtnkw@mail.gmail.com> (raw)
In-Reply-To: <20150924112555.GA21355@amethyst.visucore.com>
[-- Attachment #1: Type: text/plain, Size: 1188 bytes --]
ACK
On Thu, Sep 24, 2015 at 7:25 AM, Wladimir J. van der Laan via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> Hello all,
>
> The next major release of Bitcoin Core, 0.12.0 is planned for the end of
> the year. Let's propose a more detailed schedule:
>
> 2015-11-01
> -----------
> - Open Transifex translations for 0.12
> - Soft translation string freeze (no large or unnecessary changes)
> - Finalize and close translation for 0.10
>
> 2015-12-01
> -----------
> - Feature freeze
> - Translation string freeze
>
> In December at least I will probably not get much done code-wise (Scaling
> Bitcoin Hongkong, 32C3, end of year festivities, etc), and I'm sure I'm not
> the only one, so let's leave that for last pre-RC bugfixes and polishing.
>
> 2016-01-06
> -----------
> - Split off `0.12` branch from `master`
> - Start RC cycle, tag and release `0.12.0rc1`
> - Start merging for 0.13 on master branch
>
> 2016-02-01
> -----------
> - Release 0.12.0 final (aim)
>
> Wladimir
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
[-- Attachment #2: Type: text/html, Size: 1801 bytes --]
next prev parent reply other threads:[~2015-09-29 21:23 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 [this message]
2015-09-30 17:57 ` Luke Dashjr
2015-09-30 18:10 ` Jorge Timón
2015-09-30 19:24 ` Jeff Garzik
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_WcY9Qd7OKJTr_H0YUVo4PAkV2tKrjQ-0-iTV5ogNrQtnkw@mail.gmail.com \
--to=jgarzik@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=laanwj@gmail.com \
/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