public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Alex Waters <ampedal@gmail•com>
To: bitcoin-development@lists•sourceforge.net
Subject: [Bitcoin-development] Testing commits
Date: Tue, 6 Sep 2011 20:32:27 -0400	[thread overview]
Message-ID: <CAL0fb62WFvqFFDm=jvgG2B2Gyxj_uV_Ex-drjYHMVh08F0YrNQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 902 bytes --]

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

[-- Attachment #2: Type: text/html, Size: 1459 bytes --]

             reply	other threads:[~2011-09-07  0:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-07  0:32 Alex Waters [this message]
2011-09-07  2:59 ` Jeff Garzik
2011-09-07  3:51 ` Matt Corallo
2011-09-09 10:08   ` Alex Waters

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAL0fb62WFvqFFDm=jvgG2B2Gyxj_uV_Ex-drjYHMVh08F0YrNQ@mail.gmail.com' \
    --to=ampedal@gmail$(echo .)com \
    --cc=bitcoin-development@lists$(echo .)sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox