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
94
95
96
97
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <laanwj@gmail.com>) id 1W3ixe-0006eq-Fz
for bitcoin-development@lists.sourceforge.net;
Thu, 16 Jan 2014 09:10:02 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.214.42 as permitted sender)
client-ip=209.85.214.42; envelope-from=laanwj@gmail.com;
helo=mail-bk0-f42.google.com;
Received: from mail-bk0-f42.google.com ([209.85.214.42])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1W3ixb-0001pu-Hf
for bitcoin-development@lists.sourceforge.net;
Thu, 16 Jan 2014 09:10:01 +0000
Received: by mail-bk0-f42.google.com with SMTP id my12so1075603bkb.15
for <bitcoin-development@lists.sourceforge.net>;
Thu, 16 Jan 2014 01:09:53 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.204.229.139 with SMTP id ji11mr5121414bkb.4.1389863393055;
Thu, 16 Jan 2014 01:09:53 -0800 (PST)
Received: by 10.204.69.197 with HTTP; Thu, 16 Jan 2014 01:09:52 -0800 (PST)
Date: Thu, 16 Jan 2014 10:09:52 +0100
Message-ID: <CA+s+GJBo7iUEJTfJw2e6qcDmdHNGdDN442Svs5ikVyUL1Jm0Wg@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=485b3961867ed492f204f012c93b
X-Spam-Score: -0.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
1.0 HTML_MESSAGE BODY: HTML included in message
-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: 1W3ixb-0001pu-Hf
Subject: [Bitcoin-development] Bitcoin Core 0.9rc1 release schedule
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: Thu, 16 Jan 2014 09:10:02 -0000
--485b3961867ed492f204f012c93b
Content-Type: text/plain; charset=UTF-8
Hello all,
It has been way to long since last major release. Many improvements and new
features have been added to master since, so we'd like to do a 0.9rc1
release soon.
The current aim is next month, February 2014.
Of course there are still some open issues that need to be resolved before
release
https://github.com/bitcoin/bitcoin/issues?milestone=12&state=open
If there is something else that you're working on and needs to end up in
0.9, or know of some nasty bug in master that should absolutely be solved
first, please tell.
Wladimir
--485b3961867ed492f204f012c93b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Hello all,<div><br></div><div>It has been way to long sinc=
e last major release. Many improvements and new features have been added to=
master since, so we'd like to do a 0.9rc1 release soon.</div><div><br>
</div><div>The current aim is next month, February 2014.</div><div><br></di=
v><div>Of course there are still some open issues that need to be resolved =
before release<br></div><div><a href=3D"https://github.com/bitcoin/bitcoin/=
issues?milestone=3D12&state=3Dopen">https://github.com/bitcoin/bitcoin/=
issues?milestone=3D12&state=3Dopen</a><br>
</div><div><br></div><div>If there is something else that you're workin=
g on and needs to end up in 0.9, or know of some nasty bug in master that s=
hould absolutely be solved first, please tell.</div><div><br></div><div>
Wladimir<br></div></div>
--485b3961867ed492f204f012c93b--
|
