1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <laanwj@gmail.com>) id 1Yn0Bs-0004dl-Ma
for bitcoin-development@lists.sourceforge.net;
Tue, 28 Apr 2015 07:44:24 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 74.125.82.53 as permitted sender)
client-ip=74.125.82.53; envelope-from=laanwj@gmail.com;
helo=mail-wg0-f53.google.com;
Received: from mail-wg0-f53.google.com ([74.125.82.53])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Yn0Br-0004oa-Tq
for bitcoin-development@lists.sourceforge.net;
Tue, 28 Apr 2015 07:44:24 +0000
Received: by wgen6 with SMTP id n6so141166088wge.3
for <bitcoin-development@lists.sourceforge.net>;
Tue, 28 Apr 2015 00:44:18 -0700 (PDT)
X-Received: by 10.180.96.196 with SMTP id du4mr27141239wib.77.1430207057990;
Tue, 28 Apr 2015 00:44:17 -0700 (PDT)
Received: from amethyst.visucore.com (dhcp-089-098-016-041.chello.nl.
[89.98.16.41])
by mx.google.com with ESMTPSA id b10sm15031318wiz.9.2015.04.28.00.44.16
for <bitcoin-development@lists.sourceforge.net>
(version=TLSv1.2 cipher=RC4-SHA bits=128/128);
Tue, 28 Apr 2015 00:44:16 -0700 (PDT)
Date: Tue, 28 Apr 2015 09:44:16 +0200
From: "Wladimir J. van der Laan" <laanwj@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Message-ID: <20150428074414.GA19918@amethyst.visucore.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Spam-Score: -1.6 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(laanwj[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1Yn0Br-0004oa-Tq
Subject: [Bitcoin-development] Bitcoin core 0.11 planning
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Tue, 28 Apr 2015 07:44:24 -0000
Hello all,
The release window for 0.11 is nearing, I'd propose the following schedule:
2015-05-01 Soft translation string freeze
Open Transifex translations for 0.11
Finalize and close translation for 0.9
2015-05-15 Feature freeze, string freeze
2015-06-01 Split off 0.11 branch
Tag and release 0.11.0rc1
Start merging for 0.12 on master branch
2015-07-01 Release 0.11.0 final (aim)
In contrast to former releases, which were protracted for months, let's try to be more strict about the dates. Of course it is always possible for last-minute critical issues to interfere with the planning. The release will not be held up for features, though, and anything that will not make it to 0.11 will be postponed to next release scheduled for end of the year.
Wladimir
|
