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
84
85
86
87
88
89
90
91
92
93
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <laanwj@gmail.com>) id 1YrpBi-0003Bs-5Y
for bitcoin-development@lists.sourceforge.net;
Mon, 11 May 2015 15:00:10 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.213.52 as permitted sender)
client-ip=209.85.213.52; envelope-from=laanwj@gmail.com;
helo=mail-yh0-f52.google.com;
Received: from mail-yh0-f52.google.com ([209.85.213.52])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1YrpBh-0000wt-6T
for bitcoin-development@lists.sourceforge.net;
Mon, 11 May 2015 15:00:10 +0000
Received: by yhrr66 with SMTP id r66so36907330yhr.3
for <bitcoin-development@lists.sourceforge.net>;
Mon, 11 May 2015 08:00:03 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.236.201.66 with SMTP id a42mr10359501yho.197.1431356403687;
Mon, 11 May 2015 08:00:03 -0700 (PDT)
Received: by 10.13.250.69 with HTTP; Mon, 11 May 2015 08:00:03 -0700 (PDT)
In-Reply-To: <20150428074414.GA19918@amethyst.visucore.com>
References: <20150428074414.GA19918@amethyst.visucore.com>
Date: Mon, 11 May 2015 15:00:03 +0000
Message-ID: <CA+s+GJDtduxkc4aVL_s_vhu_jh+3XmnuP2N6UHD=FcLiiZAUmQ@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
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: 1YrpBh-0000wt-6T
Subject: Re: [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: Mon, 11 May 2015 15:00:10 -0000
A reminder - feature freeze and string freeze is coming up this Friday the =
15th.
Let me know if your pull request is ready to be merged before then,
Wladimir
On Tue, Apr 28, 2015 at 7:44 AM, Wladimir J. van der Laan
<laanwj@gmail.com> wrote:
> Hello all,
>
> The release window for 0.11 is nearing, I'd propose the following schedul=
e:
>
> 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 t=
ry to be more strict about the dates. Of course it is always possible for l=
ast-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
|
