From: "Wladimir J. van der Laan" <laanwj@gmail.com>
To: Bitcoin development mailing list <bitcoin-dev@lists.linuxfoundation.org>
Subject: [bitcoin-dev] Proposed release schedule 0.13.0
Date: Mon, 14 Mar 2016 12:18:33 +0100 [thread overview]
Message-ID: <20160314111833.GA13529@amethyst.visucore.com> (raw)
Proposed release schedule for 0.13.0:
2015-05-01
-----------
- Open Transifex translations for 0.13
- Soft translation string freeze (no large or unnecessary string changes until release)
- Finalize and close translations for 0.11
2015-05-15
-----------
- Feature freeze (bug fixes only until release)
- Translation string freeze (no more source language changes until release)
2016-06-06
-----------
- Split off `0.13` branch from `master`
- Start RC cycle, tag and release `0.13.0rc1`
- Start merging for 0.14 on master branch
2016-07-01
-----------
- Release 0.13.0 final (aim)
next reply other threads:[~2016-03-14 11:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 11:18 Wladimir J. van der Laan [this message]
2016-03-16 11:42 ` [bitcoin-dev] Proposed release schedule 0.13.0 Wladimir J. van der Laan
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=20160314111833.GA13529@amethyst.visucore.com \
--to=laanwj@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.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