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
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <ampedal@gmail.com>) id 1R1649-0001gG-FA
for bitcoin-development@lists.sourceforge.net;
Wed, 07 Sep 2011 00:32:33 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.216.43 as permitted sender)
client-ip=209.85.216.43; envelope-from=ampedal@gmail.com;
helo=mail-qw0-f43.google.com;
Received: from mail-qw0-f43.google.com ([209.85.216.43])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1R1648-0003yt-I5
for bitcoin-development@lists.sourceforge.net;
Wed, 07 Sep 2011 00:32:33 +0000
Received: by qwm42 with SMTP id 42so5353156qwm.30
for <bitcoin-development@lists.sourceforge.net>;
Tue, 06 Sep 2011 17:32:27 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.63.229 with SMTP id c37mr1566219qci.191.1315355547141;
Tue, 06 Sep 2011 17:32:27 -0700 (PDT)
Received: by 10.229.91.68 with HTTP; Tue, 6 Sep 2011 17:32:27 -0700 (PDT)
Date: Tue, 6 Sep 2011 20:32:27 -0400
Message-ID: <CAL0fb62WFvqFFDm=jvgG2B2Gyxj_uV_Ex-drjYHMVh08F0YrNQ@mail.gmail.com>
From: Alex Waters <ampedal@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Content-Type: multipart/alternative; boundary=0016e64ea3b02404a104ac4f14f1
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
(ampedal[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
0.0 T_TO_NO_BRKTS_FREEMAIL To: misformatted and free email service
X-Headers-End: 1R1648-0003yt-I5
Subject: [Bitcoin-development] Testing commits
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, 07 Sep 2011 00:32:33 -0000
--0016e64ea3b02404a104ac4f14f1
Content-Type: text/plain; charset=ISO-8859-1
I am working on the following to create a stable build environment for
testers:
- Build bitcoin 4.0 source in Windows 7
- Create a package of the build dependencies, and upload to SF
- Write up instructions for the build process
x Build bitcoin 4.0 source in Ubuntu 11
- Create a package of the build dependencies, and upload to SF
- Write up instructions for the build process
I am also compiling a list of commits that need to be tested in both
environments. If you can think of any priority commits that need testing,
and/or have a test case for them - please link the pull request in a
response to https://github.com/alexwaters/bitcoin/issues/2
This is not a requirement for pull requests, but will help process the
important/easy ones a lot faster. I would love to discuss other ways of
prioritizing pull requests, but this seems like it can get the job done for
the time-being.
-Alex Waters
--0016e64ea3b02404a104ac4f14f1
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<span class=3D"Apple-style-span" style=3D"font-family: arial, sans-serif; f=
ont-size: 13px; background-color: rgb(255, 255, 255); "><div>I am working o=
n the following to create a stable build environment for testers:</div><div=
>
<br></div><div>- Build bitcoin 4.0 source in Windows 7</div><div>- Create a=
package of the build=A0dependencies, and upload to SF</div><div>- Write up=
instructions for the build process</div><div><br></div><div><div>x Build b=
itcoin 4.0 source in Ubuntu 11</div>
<div>- Create a package of the build=A0dependencies, and upload to SF</div>=
<div>- Write up instructions for the build process</div></div><div><br></di=
v><div>I am also compiling a list of commits that need to be tested in both=
environments. If you can think of any priority commits that need testing, =
and/or have a test case for them - please link the pull request in a respon=
se to=A0<a href=3D"https://github.com/alexwaters/bitcoin/issues/2" target=
=3D"_blank" style=3D"color: rgb(0, 0, 204); ">https://github.com/alexwaters=
/bitcoin/issues/2</a></div>
<div><br></div><div>This is not a requirement for pull requests, but will h=
elp process the important/easy ones a lot faster. I would love to discuss o=
ther ways of prioritizing pull requests, but this seems like it can get the=
job done for the time-being.</div>
<div><br></div></span><span class=3D"Apple-style-span" style=3D"font-family=
: arial, sans-serif; font-size: 13px; background-color: rgb(255, 255, 255);=
">-Alex Waters</span>
--0016e64ea3b02404a104ac4f14f1--
|
