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: [bitcoin-dev] Scheduling refactors (was Re: Bitcoin Core 0.12.0 release schedule)
Date: Thu, 1 Oct 2015 06:37:22 -0400 [thread overview]
Message-ID: <CADm_WcayiGr4RO116t3Xo_=s=JqnkBCdr2ox7O0uyD1CTzkRxw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 634 bytes --]
On Thu, Sep 24, 2015 at 7:25 AM, Wladimir J. van der Laan via bitcoin-dev <
bitcoin-dev@lists•linuxfoundation.org> wrote:
> 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 freez
Proposed: Schedule a time window for merging big refactors such as
libconsensus - assuming its ready as discussed per current plan - such as
October 25-31 or November 1-7.
(and implicitly, do not merge big refactors into 0.12 outside that window)
[-- Attachment #2: Type: text/html, Size: 1056 bytes --]
reply other threads:[~2015-10-01 10:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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_WcayiGr4RO116t3Xo_=s=JqnkBCdr2ox7O0uyD1CTzkRxw@mail.gmail.com' \
--to=jgarzik@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=laanwj@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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