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-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gavinandresen@gmail.com>)
id 1UV1X2-0000hx-Cq; Wed, 24 Apr 2013 15:22:52 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.215.179 as permitted sender)
client-ip=209.85.215.179; envelope-from=gavinandresen@gmail.com;
helo=mail-ea0-f179.google.com;
Received: from mail-ea0-f179.google.com ([209.85.215.179])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1UV1X1-0005kk-HN; Wed, 24 Apr 2013 15:22:52 +0000
Received: by mail-ea0-f179.google.com with SMTP id h10so789611eaj.38
for <multiple recipients>; Wed, 24 Apr 2013 08:22:44 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.15.35.200 with SMTP id g48mr50154507eev.33.1366816964811;
Wed, 24 Apr 2013 08:22:44 -0700 (PDT)
Received: by 10.223.96.132 with HTTP; Wed, 24 Apr 2013 08:22:44 -0700 (PDT)
Date: Wed, 24 Apr 2013 11:22:44 -0400
Message-ID: <CABsx9T3ZYVosuL9MKpuK_5fJb01Yj-zBS0YGmdA-Jo4L3UHzhA@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=089e0168207aa943c804db1cdfbf
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
(gavinandresen[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: 1UV1X1-0005kk-HN
Cc: bitcoin-test@lists.sourceforge.net
Subject: [Bitcoin-development] Time for a 0.8.2 release
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: Wed, 24 Apr 2013 15:22:52 -0000
--089e0168207aa943c804db1cdfbf
Content-Type: text/plain; charset=ISO-8859-1
Consensus in #bitcoin-dev chat is that it is time to do a 0.8.2 release. A
few important bugs have been fixed, and the goal will be to get a 0.8.2
final release before the May 15'th hard fork deadline.
Pieter has already started going through the issues list; help with
testing, debugging, and fixing high-priority issues is very welcome. I'll
also be going through the issues list and marking any issues I think need
to be fixed with the '0.8.2' milestone.
If translation work needs to be done, now is a great time to do it.
We still don't have a basic QA checklist for testing of release candidates;
I'll commit to spending a little of the remaining "Bitcoin Testing Project"
bitcoins to whoever contributes to creating one.
--
--
Gavin Andresen
--089e0168207aa943c804db1cdfbf
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Consensus in #bitcoin-dev chat is that it is time to do a 0.8.2 release. A =
few important bugs have been fixed, and the goal will be to get a 0.8.2 fin=
al release before the May 15'th hard fork deadline.<div><br></div><div>
Pieter has already started going through the issues list; help with testing=
, debugging, and fixing high-priority issues is very welcome. I'll also=
be going through the issues list and marking any issues I think need to be=
fixed with the '0.8.2' milestone.</div>
<div><br></div><div>If translation work needs to be done, now is a great ti=
me to do it.<br clear=3D"all"><div><br></div><div>We still don't have a=
basic QA checklist for testing of release candidates; I'll commit to s=
pending a little of the remaining "Bitcoin Testing Project" bitco=
ins to whoever contributes to creating one.</div>
<div><br></div>-- <br>--<br>Gavin Andresen<br>
</div>
--089e0168207aa943c804db1cdfbf--
|
