📅 Original date posted:2011-09-07
🗒️ Summary of this message: Alex Waters is creating a stable build environment for testers by building Bitcoin 4.0 source in Windows 7 and Ubuntu 11. He is also compiling a list of commits that need testing.
📝 Original message: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
Matt Corallo [ARCHIVE] /
npub1e4…jxmcu
2023-06-07 02:22:53
in reply to nevent1q…qxsr
Author Public Key
npub1e46n428mcyfwznl7nlsf6d3s7rhlwm9x3cmkuqzt3emmdpadmkaqqjxmcuPublished at
2023-06-07 02:22:53Event JSON
{
"id": "985333a28856d96ba7d6ce936dace284d96a3043f6a5b6f6689736c4edbfe767",
"pubkey": "cd753aa8fbc112e14ffe9fe09d3630f0eff76ca68e376e004b8e77b687adddba",
"created_at": 1686104573,
"kind": 1,
"tags": [
[
"e",
"726977f1da0bb505603590cad5caa73bf1fc9756bc570b8803b383da16739676",
"",
"root"
],
[
"e",
"30121c753682f0c8146cdca12118467818a56aa4b2d7c524957ceffa92085c42",
"",
"reply"
],
[
"p",
"b25e10e25d470d9b215521b50da0dfe7a209bec7fedeb53860c3e180ffdc8c11"
]
],
"content": "📅 Original date posted:2011-09-07\n🗒️ Summary of this message: Alex Waters is creating a stable build environment for testers by building Bitcoin 4.0 source in Windows 7 and Ubuntu 11. He is also compiling a list of commits that need testing.\n📝 Original message:On Tue, 2011-09-06 at 20:32 -0400, Alex Waters wrote:\n\u003e I am working on the following to create a stable build environment for\n\u003e testers:\n\u003e \n\u003e \n\u003e - Build bitcoin 4.0 source in Windows 7\nWhen did it switch from 0.4 to 4.0?\nI feel like the user-facing quality of the software should not be\nover-emphasized when it really is very beta in quality.\n\u003e - Create a package of the build dependencies, and upload to SF\nhttps://bitcointalk.org/index.php?topic=4750.0 (a bit outdated, but it\nshould still work fine)\n\u003e - Write up instructions for the build process\nhttps://bitcointalk.org/index.php?topic=5851.msg86700#msg86700\nIf the instructions were updated with fresh links/versions/etc, they\nshould work 100%.\n\u003e \n\u003e \n\u003e x Build bitcoin 4.0 source in Ubuntu 11\n\u003e - Create a package of the build dependencies, and upload to SF\nNo package needed, just apt-get the relevant packages?\n\u003e - Write up instructions for the build process\ndoc/build-unix.txt is (though in some cases somewhat ubuntu-specific)\nquite good IMHO.\n\u003e \n\u003e \n\u003e I am also compiling a list of commits that need to be tested in both\n\u003e environments. If you can think of any priority commits that need\n\u003e testing, and/or have a test case for them - please link the pull\n\u003e request in a response\n\u003e to https://github.com/alexwaters/bitcoin/issues/2\nIf you are feeling lazy, I can convince jenkins.bluematt.me to churn out\nwindows and ubuntu builds almost identical to those that will come out\nof gitian (ie the same build as the official release builds) if you\nwant.\nSomething like the current jenkins scripts could also be easily hacked\nup to automatically sanity-test pull requests as they come in and catch\ncommon errors (or just sanity failures).\n\u003e \n\u003e \n\u003e This is not a requirement for pull requests, but will help process the\n\u003e important/easy ones a lot faster. I would love to discuss other ways\n\u003e of prioritizing pull requests, but this seems like it can get the job\n\u003e done for the time-being.\n\u003e \n\u003e \n\u003e -Alex Waters",
"sig": "8038b5fb111b5893a88555ce9c3fd56758341d0ada535c5cbbf9db042db490d35ef9aec7b045fe96affe0094e51c572fa9d382abbfc9a8d80416ce5e651976da"
}