public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
* [Bitcoin-development] Testing commits
@ 2011-09-07  0:32 Alex Waters
  2011-09-07  2:59 ` Jeff Garzik
  2011-09-07  3:51 ` Matt Corallo
  0 siblings, 2 replies; 4+ messages in thread
From: Alex Waters @ 2011-09-07  0:32 UTC (permalink / raw)
  To: bitcoin-development

[-- 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 --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [Bitcoin-development] Testing commits
  2011-09-07  0:32 [Bitcoin-development] Testing commits Alex Waters
@ 2011-09-07  2:59 ` Jeff Garzik
  2011-09-07  3:51 ` Matt Corallo
  1 sibling, 0 replies; 4+ messages in thread
From: Jeff Garzik @ 2011-09-07  2:59 UTC (permalink / raw)
  To: Alex Waters; +Cc: bitcoin-development

On Tue, Sep 6, 2011 at 8:32 PM, Alex Waters <ampedal@gmail•com> wrote:
> 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

May we assume you're working with / building upon the existing gitian
build stuff?

-- 
Jeff Garzik
exMULTI, Inc.
jgarzik@exmulti•com



^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [Bitcoin-development] Testing commits
  2011-09-07  0:32 [Bitcoin-development] Testing commits Alex Waters
  2011-09-07  2:59 ` Jeff Garzik
@ 2011-09-07  3:51 ` Matt Corallo
  2011-09-09 10:08   ` Alex Waters
  1 sibling, 1 reply; 4+ messages in thread
From: Matt Corallo @ 2011-09-07  3:51 UTC (permalink / raw)
  To: bitcoin-development

On Tue, 2011-09-06 at 20:32 -0400, Alex Waters wrote:
> I am working on the following to create a stable build environment for
> testers:
> 
> 
> - Build bitcoin 4.0 source in Windows 7
When did it switch from 0.4 to 4.0?
I feel like the user-facing quality of the software should not be
over-emphasized when it really is very beta in quality.
> - Create a package of the build dependencies, and upload to SF
https://bitcointalk.org/index.php?topic=4750.0 (a bit outdated, but it
should still work fine)
> - Write up instructions for the build process
https://bitcointalk.org/index.php?topic=5851.msg86700#msg86700
If the instructions were updated with fresh links/versions/etc, they
should work 100%.
> 
> 
> x Build bitcoin 4.0 source in Ubuntu 11
> - Create a package of the build dependencies, and upload to SF
No package needed, just apt-get the relevant packages?
> - Write up instructions for the build process
doc/build-unix.txt is (though in some cases somewhat ubuntu-specific)
quite good IMHO.
> 
> 
> 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
If you are feeling lazy, I can convince jenkins.bluematt.me to churn out
windows and ubuntu builds almost identical to those that will come out
of gitian (ie the same build as the official release builds) if you
want.
Something like the current jenkins scripts could also be easily hacked
up to automatically sanity-test pull requests as they come in and catch
common errors (or just sanity failures).
> 
> 
> 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 




^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [Bitcoin-development] Testing commits
  2011-09-07  3:51 ` Matt Corallo
@ 2011-09-09 10:08   ` Alex Waters
  0 siblings, 0 replies; 4+ messages in thread
From: Alex Waters @ 2011-09-09 10:08 UTC (permalink / raw)
  To: Matt Corallo; +Cc: bitcoin-development

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

I expect that I will make a lot of mistakes, and probably ask too many
questions - but I hope you can bear with me.

I've been trying to keep a low profile as I get better acquainted with the
project. I'm clearly in the company of some very smart people - and would
like to keep it that way.

I've tried to do my research on the main contributors, and it seems that
Matt is the only one to escape my Google stalking. If you have any questions
about my background - feel free to inquire.

It's difficult to ascertain what needs QA work first, so any guidance or
suggestion is appreciated. I'm available via social networks, email, phone,
fax?, IM, IRC, etc. Let me know your preference, or don't and I'll bugger
off.

I'll try to stay out of the way, and do my best to make the development
cycle easier. Let me know if I'm stepping on toes, or being annoying. I
won't be offended.

As for the commit testing, I want to have an idiot proof solution to get as
many people testing as possible (eventually). With code like this, I think
it's better to go full-auto with the ACKs.

-Alex

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2011-09-09 10:08 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-09-07  0:32 [Bitcoin-development] Testing commits Alex Waters
2011-09-07  2:59 ` Jeff Garzik
2011-09-07  3:51 ` Matt Corallo
2011-09-09 10:08   ` Alex Waters

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox