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 ) 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 ; 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: From: Alex Waters 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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
I am working o= n the following to create a stable build environment for testers:

- Build bitcoin 4.0 source in Windows 7
- Create a= package of the build=A0dependencies, and upload to SF
- Write up= instructions for the build process

x Build b= itcoin 4.0 source in Ubuntu 11
- Create a package of the build=A0dependencies, 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 respon= se to=A0https://github.com/alexwaters= /bitcoin/issues/2

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.